Developers
CAELARIO API + MCP / V1

Build data workflows, not scraping infrastructure.

One authenticated surface for immediate requests, durable jobs, hundred-target batches, recurring schedules, stored results and AI-native social data tools.

API operationalBase URL https://api.caelario.comJSON over HTTPS
01

Quickstart

Create a key and run your first durable extraction.

Read guide →
02

Authentication

Use workspace-scoped API keys safely.

Read guide →
03

Jobs

Submit, poll, cancel and export one target.

Read guide →
04

Batches

Run one operation across as many as 100 targets.

Read guide →
05

Scheduling

Run once or recur daily, weekly or monthly.

Read guide →
06

Platforms

Targets, operations and result limits by network.

Read guide →
07

MCP

Connect Caelario to Codex, Claude Code and other MCP clients.

Read guide →
FIRST REQUEST

From API key to normalized result in one call.

Create a workspace key in the customer dashboard. Use the synchronous endpoint for one bounded target, then switch to durable jobs when work needs progress, retries or export.

Open the five-minute quickstart →
cURL
curl -X POST "https://api.caelario.com/v1/extract" \
  -H "X-API-Key: $CAELARIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "instagram",
    "operation": "profile",
    "target": "nike"
  }'
01

Two execution modes

Get one bounded target inline or submit durable work that survives a closed page or connection.

02

Safe automatic retries

Caelario creates IDs internally; clients may reuse an optional idempotency key after uncertain writes.

03

Pay for delivered results

Maximum cost is reserved up front. Failed work releases it; completed work settles only delivered results.

MODEL CONTEXT PROTOCOL

Let Codex or Claude run Caelario tools.

Use the guided npm package once, then work in natural language to discover capabilities, estimate credits, run extractions, monitor jobs and create schedules.

HTTP REFERENCE

Every public endpoint. No control-plane noise.

The human reference covers the public contract, while the filtered OpenAPI document remains available for tooling and code generation.

Developer supportSend integration questions to hello@caelario.com. For failed requests, include the X-Request-ID response header—never your API key.