LIVE STATUS: /uptime·PUBLIC CATALOGUE · SOURCE-ATTRIBUTED
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
Home  /  Enterprise
ENTERPRISE · SCALE · GOVERNANCE

AI and robots, for enterprise.

The verified world-data layer for production agents and machine fleets, with a live, signed, citeable public tool catalogue plus the volume, controls and support a business needs. We ground machines, not monitor people: zero personal data by construction, sources we have the clear right to redistribute, and a verifiable audit trail on every answer. Keyless to start; keyed for rate, usage and governance.

Enterprise is in early access: tailored to a production use case, agreed asynchronously — talk to sales.

WHY TEAMS STANDARDISE ON IT

Built for production.

scale

Volume that won't hang

Keyed high-volume access over one REST API or keyless MCP. The request plane reads from cache and never blocks on a slow upstream, a degraded source returns stale-flagged data, never a hang. Reliability by design; a formal SLA comes with the self-serve Enterprise tier.

governance

Control & visibility

Per-key rate & usage controls and usage visibility, with a clear data boundary: no personal data required to read, nothing sold or shared with third parties. SSO & RBAC posture below.

defensible

Audit trail by default

Every answer is Ed25519-signed and independently time-stamped by an independent RFC 3161 authority, the verifiable record regulated teams (fintech, legal, medical) need to prove what an AI was told the moment it acted.

THE MOAT

The data only we have.

The moat isn't aggregation, it's history no one else can backfill. We measure and keep what others don't: a backfill-evident provider-latency archive, append-only signed price history, and time-series recorded live, which cannot be credibly reconstructed later without breaking the signed history after the fact. The longer your systems rely on it, the more uniquely valuable it becomes.

SECURITY & CONTROLS POSTURE, WHAT'S TRUE TODAY

Straight talk, because buyers verify.

Here is exactly where we stand. Nothing we haven't built is implied as live.

access & keys

Keyless or keyed

Keyless over MCP; API keys add per-key rate & usage controls. No data sold or shared.

provenance

Every datapoint sourced

Source, licence and freshness on every value; only data we have a clear right to redistribute.

audit trail

Signed & time-stamped

Ed25519 over canonical bytes; fingerprints time-stamped by an independent RFC 3161 authority. Independently verifiable, even against us.

sso · rbac

On the roadmap

SSO / SAML and role-based access are not live yet, included on the self-serve Enterprise tier. We won't claim them before they ship.

soc 2 · dpa

Pursued on requirement

SOC 2 and a signed DPA are pursued where the requirement is real, not claimed speculatively. Available on the self-serve Enterprise tier.

uptime · support

Status + SLA

Live status at /uptime; a formal uptime SLA and priority support come with the self-serve Enterprise tier.

PLUG IT INTO YOUR STACK

One endpoint, every client.

Keyless MCP for Claude / Cursor / Cline / Windsurf, REST with a key, a batch endpoint (≤20 calls per request), and framework adapters (LangChain, LlamaIndex, Vercel AI SDK, OpenAI Agents).

SCALE WHEN YOU'RE READY

Production data your team can trust.

Start free and keyless; move to keyed volume, governance and support when you need it, verifiable on every answer. Enterprise is in early access and tailored to a production use case — request access and tell us what your system needs to know.

Need it built for you? We'll wrap, sign & time-stamp your source into a live feed in ~5 days. done-for-you →

Access policy

InterfaceEndpointAccessUseLimit
MCP/mcpKeylessPublic read-only accessNo per-key quota; subject to service availability
REST batch/v1/batchKeylessTesting and low-volume read-only batch accessMaximum 20 calls per request
Direct RESTDocumented keyed routesX-API-KeyDirect endpoint access with usage accountingPlan quota applies
x402/v1/pro/*x402 paymentMachine-paid access on eligible premium endpointsPer-call terms are returned with HTTP 402
Enterprise/enterpriseCommercial termsDiscuss operating, support, and integration requirementsPublished or agreed service terms apply