For developers and AI agents

API v1 & MCP server

Use ABATODA through API v1 or MCP. Get structured decisions with evidence, sources, known gaps and confidence explanations — powered by the same engine as the web experience.

API v1 · LIVEMCP server · LIVEAPI keys · BETA (owner-issued)Self-serve keys & quotas · PLANNED

Quick start

bash

curl -X POST "<your-abatoda-url>/api/v1/decisions" \
  -H "content-type: application/json" \
  -H "authorization: Bearer abk_..." \
  -d '{"intent":"AI agent on WhatsApp with an LLM and a backend with auth"}'

Public reads work without a key during the early beta. Owner/admin write endpoints require a signed-in session or an API key. Add ?mode=demo only to request labelled demo fixtures; live is the default and the two are never mixed.

API v1 endpoints

POST /api/v1/decisionsLIVE

Requirement → capabilities, providers, architecture, cost, evidence, integration, unknowns.

GET /api/v1/capabilities?q=LIVE

Capability search in the live catalog.

GET /api/v1/providers?q=&capability=LIVE

Provider search, organic ordering only.

GET /api/v1/provider?provider_id=LIVE

Full provider record with claims and sources.

GET /api/v1/compare?provider_ids=a,bLIVE

Factual side-by-side. No winner.

GET /api/v1/evidence?provider_id=LIVE

Sources and claims with status and evidence type.

GET /api/v1/freshnessLIVE

Per-source fetch dates and freshness windows.

POST /api/v1/ingest · /api/v1/verification-runsBETA

Owner/admin only: source refresh and safe endpoint probes.

API keys

Keys use the abk_ prefix and are minted or revoked by organization owners and admins in the Owner console. Only a SHA-256 hash and prefix are stored; the plaintext is shown once. Usage is recorded per key.

MCP server

json

{
  "mcpServers": {
    "abatoda": { "url": "<your-abatoda-url>/api/mcp" }
  }
}

JSON-RPC over HTTP POST (initialize, tools/list, tools/call). Every tool maps onto the same engine as API v1. There is no execute tool: ABATODA recommends and routes; execution happens downstream.

search_capabilitiesLIVE
find_providersLIVE
get_decisionLIVE
compare_providersLIVE
calculate_unit_costLIVE
get_restrictionsLIVE
get_evidenceLIVE
get_architecture_optionsBETA
get_integration_routesLIVE
get_implementation_planBETA
run_verificationBETA

Legacy

/api/v0/* remains for compatibility and returns labelled demo fixtures only. Use v1 for live data.