Can I try the API before buying credits?

Yes. You receive 3 free credits on signup to test the API with no commitment, enough to validate your integration with test generations.

How many API Keys can I create?

Up to 5 active API Keys per account. Use a different key per project or environment (development, staging, production) to separate usage tracking.

Can I customize the generation prompt?

Yes. The parameters.customInstructions field adds instructions to the system prompt (max 5,000 chars). For full control, parameters.customPrompt replaces the default prompt entirely (max 50,000 chars). Combined with brand profiles (profileId), you can maintain a consistent tone and style.

What happens if generation fails midway?

Credits are automatically released if generation fails. Check the status field in the response: completed (success), partial (incomplete content, credits charged), or failed (total failure, credits refunded).

How do I adapt previously generated content?

In POST /api/v1/adapt, use the contentId field with the generation ID (cnt_xxxx) to reuse the original content without resending text. To adapt your own text, use the contentText field directly (max 50,000 chars). You must send at least one of the two.

Is there an official SDK?

No. The API is standard REST with JSON. Any HTTP client works: fetch, axios, requests, curl, etc. The code examples on this page are copy-paste ready for production.

How long does a generation take?

Depends on length: short content (300-500 words) takes 10-15 seconds, medium (800-1,200) about 15-25 seconds, long (1,800-2,500) between 25-40 seconds, and extra_long (3,000-5,000) can reach 60 seconds. Set a timeout of at least 90 seconds in your HTTP client.

Does the API support streaming (SSE)?

No. The API is synchronous: it returns the complete response in a single JSON call when generation finishes. There are no Server-Sent Events or a status endpoint to poll; set a generous timeout (at least 90 seconds) in your HTTP client.

Is there technical support for the API?

The contact form is open to any user. Having credits also activates the Support Center in your account, where you open technical tickets with tracking, attach screenshots and get an email notification when we reply, with more personalized attention.

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: the JSON schema is built dynamically per request and forces the model to follow its structure, minimizing omitted or malformed 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

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

7Multi-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",
    "contentType": "blog_post",
    "parameters": { "length": "long", "tone": "professional" }
  }'

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, press_release, 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 JSON object with the content, its SEO metadata, and cited sources.

{
  "id": "cnt_a1b2c3d4e5f6",
  "topic": "SEO trends 2026",
  "content_type": "blog_post",
  "language": "es",
  "status": "completed",
  "created_at": "2026-01-15T10:30:00Z",
  "output_format": "html",
  "html": "<h1>SEO Trends 2026</h1><p>...</p>",
  "markdown": "",
  "word_count": 1200,
  "summary": "Resumen del contenido generado.",
  "missing_fields": [],
  "meta_seo": {
    "title": "SEO Trends 2026",
    "description": "Descubre las tendencias SEO de 2026...",
    "slug": "seo-trends-2026",
    "keywords": ["seo", "trends", "2026"]
  },
  "sections": [
    { "type": "paragraph", "heading": "Introducción", "level": 2, "content": "..." }
  ],
  "sources": [
    {
      "title": "Google Blog",
      "url": "https://developers.google.com/...",
      "domain": "developers.google.com",
      "index": 1,
      "accessed_at": "2026-01-15"
    }
  ]
}

idUnique generation identifier (cnt_xxxx)

topicTopic sent in the request

content_typeGenerated content type (article, blog_post, etc.)

languageContent language: es or en

statusStatus: completed, failed, or partial

created_atISO 8601 creation date

output_formatContent format: html, markdown, or plain_text

htmlFull generated content, in the format indicated by output_format

markdownMarkdown version of the content when that format is requested; empty string otherwise

word_countWord count of the content

summaryContent summary if requested (includeSummary), or null

missing_fieldsRequested fields that could not be generated; empty if everything was generated

meta_seoSEO metadata: title, description, slug, and keywords (or null if includeMetaSeo=false)

sectionsStructured content sections with type, heading, level, and content

sourcesCited sources with title, url, domain, index, and accessed_at (if includeSources=true)

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., codeLanguage without includeCode)

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

Developer support

We answer your integration questions through the contact form, available to any user. Having credits activates the Support Center in your account: you open tickets with tracking, attach screenshots and we email you when we reply, with more personalized attention.

Go to support