Glossary

30 terms, plain-English definitions, cross-linked. Cite any of these from your own docs or LLM answer engine — every entry is its own page with stable URL.

x402

An open standard for HTTP-native programmatic payments using stablecoins, hosted by the x402 Foundation under the Linux Foundation.

Payment-Identifier (x402 extension)

An x402 extension that lets buyers attach a stable identifier to retries so vendors can deduplicate payment processing.

x402 Facilitator

A trusted third-party service that verifies and settles x402 payments on behalf of vendors who don't want to run their own settlement layer.

Coinbase's discovery layer for x402-payable services. A live catalog with semantic search, pricing data, and trust signals.

A public marketplace for x402 services with live pricing, volume data, top lists, and integration guides — built for both humans and agents.

Idempotency (in payments)

A guarantee that retrying the same paid call with the same identifier results in at most one charge.

agentic

Agentic Commerce

Commerce in which one or both parties are AI agents acting autonomously rather than humans clicking buttons.

A goal + budget + policy bundle that an agent (or a user) submits to Mission Control. The unit of work that gets quoted, paid for, verified, and audited.

The component that picks one x402 service per planned step, scoring candidates by relevance, success rate, verification pass rate, latency, and cost.

The orchestration layer that walks a Mission through plan → quote → policy → execute → verify → complete with durable state transitions.

MCP (Model Context Protocol)

An open protocol for tool / context exposure to AI agents. Mission Control ships an MCP server with 8 tools.

Company Research (mission type)

Mission template that produces an investment memo or sales brief on one company, with multi-source verification.

Crypto Due Diligence (mission type)

Mission template that profiles a token's team, tokenomics, on-chain risk signals, and off-chain reputation.

Market Research (mission type)

Mission template for sector scans, trend reports, and market sizing — typically the cheapest mission ($1–$5).

Lead Enrichment (mission type)

Mission template for bulk account or contact enrichment — adds firmographic, technographic, and signal data to a list of leads.

Competitor Research (mission type)

Mission template for ranked competitive landscapes — who competes with X, on what dimensions, with which advantages.

governance

The pure-function authorization layer that decides every spend before the wallet signs anything. No LLM in this path.

Wallet Kill Switch

An operator-tripable circuit that halts every paid call across the org until cleared. Two layers: env-locked and runtime-API.

Hash-Chained Audit Ledger

An append-only event log where every entry references the SHA-256 hash of the previous entry. verifyChain() detects tampering.

A human-in-loop checkpoint that fires when policy returns requires_approval. Mission halts in awaiting_approval until granted or denied.

Per-Vendor Rate Limiter

Token bucket per provider_id, default 10 req/sec + 20 burst. Stops a misbehaving prompt from hammering one vendor.

OpenID Connect single sign-on. Mission Control accepts JWTs from any configured IdP (Okta, Auth0, Azure AD, Google Workspace).

verification

Provider Quality Score

A computed [0,1] score per provider, derived from real execution data over a 30-day rolling window.

Provider Certification

An application + review process that promotes a provider's certification_status to certified after 5 criteria pass.

Result Verifier

A three-layer post-execution check: deterministic (schema, freshness, sources), cross-source consistency, and an LLM evaluator signal.

A buyer-initiated claim against a completed mission. Moves the mission to disputed; resolution is refunded, partial_refund, or denied.

Webhook Signatures (HMAC-SHA256)

Mission Control signs every webhook delivery with HMAC-SHA256 over `${timestamp}.${body}`. Receivers verify with @mc/sdk.

economics

A cryptocurrency pegged to a fiat reference (typically USD) — the unit of account for x402 payments. USDC is the default in Mission Control.

Orchestration Fee

Mission Control's revenue model: a percentage on top of vendor spend, charged per completed mission.

Billing (orchestration + vendor spend)

Mission Control tracks two revenue streams per mission: vendor settlement (x402 to providers) and orchestration fee (to Mission Control).

Stripe Meter Export

An endpoint that emits Mission Control's billing_events in Stripe meter_event format, ready for /v1/billing/meter_events.