Docs
API reference
The same doors over HTTP. Send your key as a bearer token.
Base address: your app address, for example https://app.overscore.tech. Every request sends Authorization: Bearer ovs_…. Bodies and answers are JSON. The CLI is a thin layer over exactly these routes, so anything it can do, a script can do.
Read
GET /index every table by tier, one line each
GET /index/{dish}/{table} columns, samples, freshness, lineage
GET /tables GET /tables/{dish}/{table} GET /schema
POST /query {"sql": "select …"}
GET /find/{dish}/{table}?q= words in a table of messages or tickets
GET /context?q= one search over facts, notes and tablesPut data in
POST /in/{dish}/{table} one JSON object or a list; the table is created on first post
POST /files/{dish}/{table} CSV, TSV, Excel, JSON, Parquet (replaces the table; versions kept)
POST /sheets/{dish}/{table} {"url": "…", "every_minutes": 15}
POST /hooks GET /hooks DELETE /hooks/{token}
POST /connectors/{name} {"key": "rk_live_…"} and the like
PUT /links/{dish} POST /links/{dish}/copy DELETE /links/{dish}Models and definitions
GET /models PUT /models/{dish}/{name} POST /run/{dish} POST /tests/{dish} GET /models/export
GET /metrics PUT /metrics/{name} POST /metrics/{name}/run POST /metrics/{name}/check
GET /graph/{dish} lineage as nodes and edgesContext and the inbox
GET /context/cards POST /context/cards/{id}/approve|ignore
POST /context/arrivals something heard, to be turned into a card
GET /context/facts/{table} PUT /context/facts/{table}/{key}
POST /interview POST /interview/{conv}Worklists
GET /work GET|PUT /work/{dish}/{table}/fields POST /work/{dish}/{table}/mark GET /work/{dish}/{table}/historyDashboards and reports
GET /dashboards PUT /dashboards/{slug} POST /dashboards/{slug}/publish GET /dashboards/{slug}/numbers
GET /datasets PUT /datasets/{name} POST /datasets/{name}/run
POST /reports GET /reportsAgents
POST /mcp the MCP address; add it to Claude Code, Cursor or any MCP client