Skip to main content
This guide uses Direct Execute mode with Meridian pinned by tool ID. Execute returns the typed market-data response directly and charges the method’s published per-call price. Query mode remains available when Context should interpret a natural-language question.

1. Create a Context API key

  1. Sign in at ctxprotocol.com.
  2. Configure the wallet spending cap required by Context.
  3. Fund the Context wallet for paid tool calls.
  4. Create an API key under Settings → API Keys.
Store the key in an environment variable. Never embed it in browser code or commit it to a repository.

2. Install an SDK

3. Execute Meridian

4. Inspect the response

result.result["rows"] is a DataFrame-ready list of normalized row objects. Each Execute response also reports method and session billing metadata. Meridian rows use canonical exchange, product, and time identities. Optional response sections include:
  • columns: names, types, units, and data families.
  • coverage: what exists for each exchange/product/range.
  • provenance: the source and collection lineage.
  • warnings: explicit limitations or source-limited values.
Do not infer missing values as zero. For a quality audit, repeat the narrow query with coverage=true and classify returned nulls against the coverage declarations.

Query mode

Use pinned Query mode when Context should select methods, verify evidence, and synthesize a natural-language answer:

Next steps

TypeScript integration

Python integration

Official MCP endpoint

Futures reference

Pricing and limits