mocop
Browse · Docs · Guide · Analyze

Aard REST API

API by Aard · rest

Four tools — discover, inspect, ask, build_url — each a POST /v1/{tool} taking one flat JSON object of arguments and returning the same output the MCP tool of that name produces. The tools return catalogue metadata and exact publisher requests, never observations: execute a returned plan client-side and query the parsed file locally. Authenticate with an API key minted at https://aard.ai/account/keys, sent as Authorization: Bearer aard_live_…. MCP OAuth tokens are not accepted here. Keys are bound to the account's plan: its tool entitlements and monthly call cap (https://aard.ai/pricing). A call is charged only when the origin answers with a result — a 4xx, 429 or 502 is refunded rather than charged. The API is server-to-server: /v1/* sends no CORS headers, so a browser-hosted client cannot call it directly. Every /v1/{tool} response carries X-Aard-Request-Id. Every error is {"ok": false, "error": "<code>"[, "detail": "…"]}; a 400 for an unknown or missing…

Endpoint: https://api.aard.ai/

Verification: observed. Source: crawl.

Capabilities (5)

  • Gateway health
  • Resolve a data question into ranked candidates and exact source requests
  • Prepare an exact source request for a known dataflow
  • Find official datasets about a topic
  • Read a known dataflow's structure
About · Contact · Privacy