Access surfaces
Extralt exposes the same customer dataset through several deliberately different surfaces. Availability in one surface does not imply that every other surface has the same operation or result shape.
Coverage matrix
| Capability or data | Dashboard | Public API | MCP | File export | Query | Dashboard Agent |
|---|---|---|---|---|---|---|
| Robots | Create, inspect, use, delete | Create, list, read, delete | Prepare, list, inspect, delete | No | No | Read; can prepare a Robot build for approval |
| Runs | Create, inspect, restart, stop | List, create, read, restart, stop | List, start, inspect, retry, stop | No | No | Read; can prepare an approved Run |
| Schedules | Create, edit, pause, resume, delete | Full lifecycle | Full lifecycle | No | No | Read; can prepare an approved Schedule |
| Imports | Create and inspect | Create and read status | Start and inspect status | Resulting Captures can be exported by Import | Captures can be scoped to one Import | Read-only |
| Captures | Browse and inspect | List and count | List, count, export | JSONL or Parquet by Run or Import | Yes, optionally scoped to one Run or Import | Yes, with a persisted Query result |
| Enrichments | Create, inspect, stop | List, create, read, stop | List, start, inspect, stop | No | No | Read; can prepare an approved Enrichment |
| Items | Browse and inspect | List and detail | List and inspect | JSONL or Parquet in the dashboard | Yes, optionally scoped to one Enrichment | Yes, with a persisted Query result |
| Relationships | Browse the connected model | No dedicated v1 relationship route | No dedicated tool | No | Yes, across the connected Explore model | Yes, through custom Query |
| Changes | Browse the dedicated Explore view | No dedicated v1 Changes route | No dedicated tool | No | No standalone custom Query surface | No dedicated Changes tool |
| Current markets and Variant evidence | Browse and drill down | Overview, facets, current markets, Variant metadata, current Offers, and history | Same supported evidence | No dedicated file export | Yes through the connected Explore model | Yes through custom Query |
| Four packaged Analyses | Dedicated pages | Four versioned pageable routes | All four Analyses | No dedicated file export | Separate from custom Query | Runs the same contracts and links to their pages |
The generated OpenAPI document is authoritative for public routes, filters, request fields, response schemas, and page limits. MCP publishes its own tool schemas and is documented in Connect through MCP. Dashboard-only and Agent-only operations are not public API contracts.
Public API
The public API exposes stable v1 Extract, Enrich, and Explore resources. Explore provides overview and facets, current market evidence, separate Variant metadata, current-Offer and history resources, and all four packaged Analyses.
There is no general public SQL endpoint or public materialization mutation. Final analytical entities are published as part of the Enrichment lifecycle and read through the supported Explore routes.
MCP
MCP exposes the customer-facing API capabilities as task-oriented tools for compatible agents. It uses browser OAuth and the organization selected during consent rather than an API key or an organization field in tool inputs. See Connect through MCP for setup and access rules.
Dashboard Query
Dashboard Query supports three product targets:
- Captures from all data, one Run, or one Import;
- Items from all data or one Enrichment;
- Explore across Products, Variants, Listings, Offers, Reviews, and Stores.
For Explore, the customer asks one question without choosing a table. Extralt loads the connected data model, including allowed entities, fields, relationships, and canonical current-state definitions, then generates a bounded read query. The persisted artifact keeps the question, SQL, result, status, and truncation state.
Query returns at most 100 rows and is not pageable. It is a first-party dashboard surface, not a public v1 endpoint or direct ClickHouse connection. ClickHouse's reader role enforces read-only access, organization row policies, and resource ceilings; the API adds query-size, time, row, and response-size budgets.
Dashboard Agent
The Agent can inspect the operational resources already represented in the dashboard, run the four packaged Analyses, and use the same persisted Query surface for Captures, Items, and the connected Explore model.
It can also prepare Robot, Run, Schedule, and Enrichment operations. Those operations execute only after explicit dashboard approval. Imports remain read-only through the Agent.
Subscription access
Writes require an active subscription. The 30-day post-subscription grace period is read-only and includes available exports. Grace also permits stopping active work, pausing schedules, and replaying a completed idempotent API request; those exceptions cannot create new work or consume credits. Customer data access is blocked after grace until the organization is reactivated.