Curated data sources

Making a call

Every method is forwarded. /v1/data/:source/* passes the HTTP verb, the query string (including repeated parameters, which arrive upstream as a repeated key) and the JSON body straight through to the operation the path resolves to.

Authenticate with Authorization: Bearer <key>. Mint a key in the dashboard at app.superagnt.com.

curl "https://api.superagnt.com/v1/data/<source>/<endpoint>?limit=25" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

What you pay

Every successful response carries its own price. meta.costCents is the amount actually charged for that call, after any discount on your account, and the two remaining balances sit beside it. You never need a second round trip to find out what a call cost or what is left.

{
  "success": true,
  "data": { "...": "the upstream payload, normalized" },
  "meta": {
    "costCents": 1,
    "purchasedBalanceCents": 4820,
    "subscriptionRemainingCents": 1500,
    "cached": false,
    "latencyMs": 412
  }
}

Pricing is set per slug, with optional per-endpoint overrides where one operation is materially more expensive than the rest of its source. Some sources are variable-cost by nature: the web and seo sources price a call by what the request actually did, so the platform bills the real upstream-reported cost rather than the pre-call estimate. The estimate is only the balance gate.

Failed calls cost nothing. A 4xx, a 5xx, an upstream timeout, and an upstream that returns HTTP 200 with a failure body inside it are all billed at zero and logged as errors.

Pagination

Curated sources keep each upstream's own pagination convention. Most commonly that is a dedicated continuation operation: you call the list endpoint, take the continuation token out of the response, and feed it to the matching …_continuation operation. Others page by number or by offset.

There is no single platform-wide cursor on this surface, so check the endpoint you are calling in the reference rather than assuming. Cursors on this platform exist only on the two webhook delivery lists; the workspace database and /v1/usage use limit and offset.

From an agent

Over MCP the same operations appear as tools named data_<slug>_<operationId>, for example data_reddit_search_posts. Same validation, same pricing, same credit balance as REST.

claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
claude mcp login superagnt

Curated sources are opt-in, so a fresh server does not list hundreds of tools you did not ask for. Find a source with agnt_tools_search, then turn it on with agnt_tools_enable and the family id data:<slug>, for example { "families": ["data:x"] }. The first-party agnt source is the exception: it is served on the base connection and needs no enable.

Migrating off the pre-/v1/data path