If we can’t prove it, nothing returns.

Connect an agent, call the API, or evaluate a gate. Every answer carries a level, a source, and a cost — or it refuses, and that costs nothing.

Quickstart Connect your agent Get an API key

terminal

curl -X POST https://api.metera.xyz/v1/ask \
  -H "Authorization: Bearer mk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"SOL price"}'

Connect your agent

Give the agent you already use everything it needs to add Metera itself: the MCP command, where to get a key, and the two calls worth knowing first.

Agent Prompt

Help me connect to Metera. Read https://metera.xyz/docs/mcp first. Then: 1. Install the MCP server: claude mcp add --transport http metera https://api.metera.xyz/mcp --scope user 2. Create an API key in the Metera dashboard and use it as a Bearer token (mk_live_...) for any direct HTTP calls. 3. Call ask for a verified fact, or evaluate_gate before signing a swap. Check verification.level on the response before acting on it — Metera refuses rather than guessing, and a refusal costs nothing.

Browse the docs

Introduction

What Metera is, and what it guarantees.

Quickstart

Zero to a verified call, three ways.

Verification levels

single_source, consensus, anchored.

API reference

Endpoints, the delivery object, error codes.

MCP

Verified data as a tool for your agent.

Gates

Compose verified facts into an allow/refuse decision, with your policy.

Webhooks

SDK

The @metera/sdk TypeScript client.

Keys & environments

Live and test keys, how to manage them.

Credits & billing

Credits, the two cost fields, rate limits.

Agents

Scheduled, verified data collection.

For data providers

List a source, test it, get paid on delivery.

$METERA token

Utility at launch, and what is roadmap.

Known limits

What is live, and what verification cannot catch.