STUDIO API for Developers

APISDOM multi-layer generation engine: adaptive web search, verified citations and structured SEO. Integrate it into your CMS, blog or app. Not a wrapper — it's proprietary technology.

Get API Key View full documentation

APISDOM Multi-Layer Technology

The Studio API is not a simple Claude proxy. It's a proprietary engine with over 15 internal layers between frontend and backend. Here are the highlights:

1Adaptive web search — 5-level decision tree that determines when, how much and whether to search based on topic, content type and temporal references

2Structured Outputs with constrained decoding — JSON schema is built dynamically per request; it's physically impossible for the model to omit required fields

3Versioned SKILL prompts — hierarchical chain: SKILL.md → brand profile → custom instructions, with LRU cache for performance

4Verified citations with deduplication — native Anthropic citations merged with JSON sources, deduplicated and scored by relevance

5Post-generation validation — verifies ALL requested fields exist with real content; automatically marks partial results

6Progressive 8-phase streaming — SSE with incremental per-section delivery, real-time status throughout the entire generation process

7Persistent brand profiles — tone, style and custom instructions per project, automatically injected into every generation context

8Multi-level intelligent fallback — rate limit detection → automatic Haiku retry + admin emergency model override

…plus 7+ additional layers including SHA-256 authentication, configurable rate limiting, audit logging and automatic structured SEO.

Quick Start

Get your API Key

Buy credits

Call the endpoint

Code Examples

curl -X POST https://studio.apisdom.com/api/v1/generate \
  -H "Authorization: Bearer sk_studio_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"topic": "SEO trends 2026", "language": "es"}'

Authentication

All requests require your API Key in the Authorization header.

Authorization: Bearer sk_studio_your_api_key

API Documentation

POST /api/v1/generate

Generate SEO-optimized content

POST /api/v1/adapt

Adapt content for social media

GET /api/v1/platforms

List available platforms with limits

GET /api/v1/credits

Check user credit balance

GET /api/v1/usage

Usage summary by period (day, week, month)

Parameters

topicContent topic (required)

languageLanguage: es or en

contentTypeType: article, blog_post, tutorial, newsletter, social_post, product_description, documentation, landing_page, case_study, comparison, listicle, faq, how_to, opinion

lengthLength: short, medium, long, extra_long

toneTone: professional, casual, academic, conversational, persuasive, technical, journalistic, educational, inspirational, authoritative

outputFormatFormat: html, markdown, plain_text

Response Structure

Each generation returns a complete JSON object with content, SEO metadata, verified sources, and usage metrics.

{
  "id": "cnt_a1b2c3d4e5f6",
  "created_at": "2026-01-15T10:30:00Z",
  "status": "completed",
  "language": "es",
  "content_type": "blog_post",
  "content": {
    "format": "html",
    "body": "<h1>SEO Trends 2026</h1><p>..."
  },
  "length_words": 1200,
  "meta_seo": {
    "title": "SEO Trends 2026",
    "description": "Discover the top...",
    "slug": "seo-trends-2026",
    "og_title": "SEO Trends 2026",
    "og_description": "..."
  },
  "sections": [
    { "title": "Introduction", "body": "..." }
  ],
  "sources": [
    {
      "title": "Google Blog",
      "url": "https://...",
      "snippet": "...",
      "relevance": 0.95
    }
  ],
  "usage": {
    "input_tokens": 1250,
    "output_tokens": 3400,
    "web_searches": 8,
    "model": "claude-sonnet-4-5-20250929"
  }
}

idUnique generation identifier

created_atISO 8601 creation date

statusStatus: completed, failed, or partial

content.formatRequested format (html, markdown, plain_text)

content.bodyFull generated content (HTML, Markdown, or plain text)

length_wordsWord count of the content

meta_seoSEO metadata: title, description, slug, og_title, og_description (if include_meta_seo=true)

summaryContent summary (if include_summary=true)

table_of_contentsTable of contents with id and title per section (if include_table_of_contents=true)

sectionsStructured content sections with title and body

qaRelated questions and answers (if include_qa=true)

sourcesCited sources with title, url, snippet, and relevance (if include_sources=true)

code_blocksCode blocks with language, code, and description (if include_code=true)

usageMetrics: input_tokens, output_tokens, web_searches, model

Rate Limiting

The API includes rate limiting headers in ALL responses so you can monitor your usage.

X-RateLimit-LimitMaximum requests per time window

X-RateLimit-RemainingRemaining requests in the current window

Retry-AfterSeconds to wait before retrying (only on 429)

Default limit: 30 requests/minute per API Key. The system applies the lower of the key limit and the global maximum (30 req/min).

Credit System

Each generation consumes credits based on content type and length. Adaptations cost 1-2 credits depending on the number of platforms.

Cost per content type

social_post, product_description → 1 credit

blog_post (short/medium) → 2 credits

article (medium), newsletter, documentation, landing_page → 3 credits

tutorial → 4 credits

article (long/extra_long), comparison, case_study → 5 credits

Adaptation (1-3 platforms) → 1 credit

Adaptation (4-7 platforms) → 2 credits

X-Credits-Used

Credits consumed in this request (X-Credits-Used header)

If you don't have enough credits, you will receive a 402.

Error Codes

400 — Invalid parameters or empty topic

401 — Invalid or missing API Key

402 — Insufficient credits

422 — Incompatible parameters (e.g., include_code without code_language)

429 — Rate limit exceeded (see Retry-After header)

500 — Internal server error

502 — Content generation failure

Idempotency and Duplicates

Each generation produces a unique ID (cnt_xxxx). If your request fails due to a network timeout, check the id field in the response before retrying to avoid duplicate charges.

Credit purchases use Stripe idempotency tokens to ensure the same payment is never processed twice.

Integration FAQ

Complementary APIs

If you generate content with Studio, these APIs can extend your pipeline: moderate reader comments, analyze response sentiment, forecast traffic trends, or auto-suggest related articles.

Sentiment API (DistilBERT)

Analyze reactions to your publications. Combine with Studio to measure generated content impact.

Moderation API (Toxic-BERT)

Filter toxic comments on your blog or CMS. Useful if you publish content with a comments section.

Prediction API (Chronos-2)

Forecast traffic or content demand by date. Helps plan when to publish.

Recommendations API (MiniLM)

Suggest similar articles via semantic similarity. Ideal for ‘related posts’ sections.

Real-world example: viral.apisdom.com uses the Prediction API to deliver time series forecasting in production. viral.apisdom.com

Full technical documentation with examples in 5 languages: apisdom.com/documentacion

API Pricing

Same packs as the web panel. 1 generation = 1-5 credits depending on type and length.

View credit packs