Cloud Stacks
Cloud Stacks are digital entities within Search Atlas designed primarily as tools for generating backlinks, which contribute to improving the visibility and ranking of web content in search engine results. This documentation covers the technical implementation details for working with Cloud Stacks via the API.
Authentication
All API requests require Bearer token authorization:
Authorization: Bearer <API_TOKEN>
Cloud Stack Pricing
Each Cloud Stack is priced at 15 Hyperdrive credits (equivalent to $15). Credits are deducted once, at the time of Cloud Stack creation (the content generation phase), prior to publishing.
- No additional credits are charged when you later select sites and publish the stack.
- Generated content consumes credits even if it is not published later.
- Credits are non-refundable once used.
- If a generation attempt fails and is retried, verify your HDC ledger to confirm only successful creations were billed.
Cloud Stack Status Flow
Pending → Generating → Generated → Publishing → Published
Unpublished: Removed after publication
Provider Status:
- HTML_CREATED: Publishing content
- PUBLISHED: Successfully published
- PUBLISHING_FAILED: Failed to publish
- INDEXING: Indexation in progress
- INDEXED: Published and indexed successfully
- INDEXER_SYNC_FAILED: Indexing failed
- NOT_INDEXED: Could not index content
Creating a Cloud Stack
Create a new Cloud Stack associated with either a Knowledge Graph or OTTO Project.
Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/
Payload Example:
{ "target_url": "https://example.com/about-us/", "keywords": ["SEO"], "knowledge_graph": "knowledge_graph_id" // Alternatively, "otto_project": 267 }
Manual Workflow Required After Creation
Creating a Cloud Stack does not automatically generate, approve, or publish content. After creation you must complete the following steps:
- Trigger AI content generation via the Build endpoint.
- Review and approve the generated content.
- Select target sites (cloud stack providers) for deployment.
- Deploy to publish.
Stacks that appear stuck or 'failed' often simply require manual approval. If you have many stacks, increase the results-per-page in the UI to locate any awaiting approval.
Building Cloud Stack Content
Trigger content generation via AI.
Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id/build/
Deploying Cloud Stack Content
Deploy content to specified providers. No additional HDC are charged at this step.
Endpoint: POST https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id/deploy/
Payload Example:
{ "cloud_stack_providers": [1, 2, 3, 4, 5] }
Retrieving Cloud Stack Content
Retrieve detailed cloud stack information.
Endpoint: GET https://sa.searchatlas.com/api/cg/v1/cloud-stack-contents/:cloud_stack_id
List Cloud Stack Providers
List available cloud stack providers.
Endpoint: GET https://sa.searchatlas.com/api/cg/v1/cloud-stack-providers
Troubleshooting
- Repeated generation failures with a populated Knowledge Graph: Check whether the affected stacks are actually awaiting manual approval rather than failed. Adjust pagination/results-per-page filters in the UI to locate them.
- HDC overcharge concerns: Credits are charged only at the moment of Cloud Stack creation. Selecting sites and publishing will not consume additional HDC. If your total deduction does not match the number of successfully created stacks × 15 HDC, contact support with the affected stack IDs.
- Stacks stuck in 'Generating': Confirm the Build endpoint was triggered and that the Knowledge Graph is fully populated; retry generation if needed.
Postman Collection
Available in the OTTO Cloud Stacks Postman collection. See the Search Atlas Knowledge Base for additional details.