Strategy
Value Proposition and Use Cases
Cortex is the commerce coordination layer for autonomous agents. Payments move value; Cortex makes the surrounding commerce context trustworthy: merchant identity, service discovery, delegated budgets, quote commitments, license rights, receipts, disputes, reputation, and analytics.
View full markdown analysisCore Value Proposition
AI agents
- Discover registered merchants and services before spending.
- Verify hosted catalog, quote request, and quote response documents by hash.
- Verify quote terms, payment rail, token, amount, resource, and expiry.
- Spend under delegated merchant, token, facilitator, per-payment, and daily limits.
- Use wallet transfers, ERC-20 transfers, swaps, facilitator flows, or x402.
- Check machine-readable license rights before using purchased data, reports, API output, content, or compute results.
- Record receipts, disputes, and reputation signals for future decisions.
Merchants
- Publish verifiable merchant, payout, service, and capability records.
- Exchange hosted quote request and quote response documents with agents.
- Commit exact quote terms before payment.
- Publish license tiers and post-payment rights records without replacing existing billing or API-key systems.
- Accept multiple payment rails without rebuilding trust infrastructure.
- Build portable fulfillment history through receipts and trust signals.
- Surface agent refund-abuse or dispute patterns.
Infrastructure partners
- Make agent payments legible, policy-controlled, and auditable.
- Standardize merchant, service, quote, license, receipt, dispute, and reputation data.
- Drive Base stablecoin and ERC-20 transaction volume.
- Feed wallets, facilitators, marketplaces, dashboards, risk engines, and support tools.
Use-Case Examples
Use case 1
Agent buys an API result with x402
A merchant publishes a service catalog, the agent submits a hosted quote request, Cortex normalizes and verifies the x402 payment requirement, and a receipt records settlement.
Use case 2
Agent pays a merchant with USDC
A merchant publishes a hosted quote response for a direct stablecoin payment, the agent verifies the quote, pays from its smart account, and the receipt adds commerce context.
Use case 3
Agent swaps into the required token
The agent holds one asset, the merchant requires another, and Cortex policy controls both the swap target and final merchant payment.
Use case 4
Agent buys licensed data or a paid report
A provider publishes a Cortex license after payment, the agent stores the license hash as inventory, and check_license determines whether commercial output, training, redistribution, or derivatives are allowed.
Use case 5
Enterprise gives an agent a daily budget
A company allows specific merchants, tokens, facilitators, rails, and spend limits while receipts and licenses create an audit trail.
Use case 6
Merchant builds reputation with agents
A merchant's completed orders, fulfillment signals, and dispute history become portable trust data across marketplaces and agents.
Use case 7
Refund and dispute workflow
Agents can flag missing or malformed fulfillment, while merchants can identify repeated refund abuse from agents.
Use case 8
Marketplace uses Cortex as its trust backend
Marketplaces can index Cortex data for discovery and ranking while agents verify claims against Base.
Use case 9
Base or Coinbase drives agentic stablecoin volume
Cortex creates measurable onchain commerce activity with merchant count, service count, rail mix, receipts, disputes, and active agents.
Use case 10
Compliance-aware agent purchasing
Agents can restrict purchases to verified merchants, approved service categories, and attestable compliance metadata.
Use case 11
Agent-to-agent service commerce
One agent can register as a merchant, sell a service, receive payment, and build reputation with other agents.
High-Value Initial Wedges
Paid API calls for agents
The strongest starting wedge because agents already need data, inference, enrichment, research, and automation APIs.
Licensed data, reports, and agent-usable content
A concrete wedge now that Cortex has V1 license documents, REST inventory/check routes, and MCP list/check tools.
Enterprise agent spend controls
A clear buyer problem: companies need agent autonomy without unconstrained wallets.
Merchant reputation for agent buyers
Every transaction can create trust data that improves future routing and discovery.
What Still Needs to Be Added or Strengthened
| Area | Needed work |
|---|---|
| Product | Deeper license UX in overview, onboarding, dashboards, and purchase simulator; stronger schema validation for all hosted document types; richer seeded demos; and better receipt polling/decoded error UX. |
| Trust | Merchant verification, service attestations, agent risk signals, dispute resolution roles, and explainable reputation scoring. |
| Enterprise | Organization policy, team roles, approval flows, budget dashboards, accounting/compliance exports, license reporting, compliance metadata, and vendor review attestations. |
| Ecosystem | Wallet and smart account integrations, real x402 facilitator integrations, merchant templates, AgentKit/MCP examples, marketplace integrations, and partner analytics. |
Recommended Messaging
- The commerce layer for autonomous agents.
- Policy, quotes, licenses, receipts, disputes, and reputation for agent payments.
- Cortex makes agent transactions verifiable.
- Payments move value. Cortex makes the commerce context trustworthy.
- Base-native infrastructure for agentic commerce.