Cortex Licenses
Cortex Licenses turn payment into permission. Providers can keep Stripe, AWS Marketplace, x402, API keys, or invoices while publishing a canonical license record agents can verify before using a protected resource.
Why It Matters
Payments prove money moved. Licenses tell an agent what it is allowed to do with what it bought: read a report, analyze a dataset, produce commercial output, create derivatives, redistribute data, or use results for model training.
This helps agents avoid unauthorized use, helps providers sell to agent buyers without replacing their billing stack, and gives enterprise buyers an audit trail that connects quote, receipt, fulfillment, and usage rights.
License Document
{
"schema": "cortex.license.v1",
"issuer": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"holder": "0x1111111111111111111111111111111111111111",
"merchant_id": "1",
"service_numeric_id": "1",
"service_id": "company-enrichment-v1",
"asset_id": "dataset:company-enrichment:v1",
"quote_hash": "0x1111111111111111111111111111111111111111111111111111111111111111",
"receipt_id": "42",
"rights": ["read", "analyze", "commercial_output"],
"constraints": {
"commercial_use": true,
"derivative_use": true,
"model_training": false,
"redistribution": false
},
"expires_at": 1798761600
}Seller Flow
- Register the merchant and service.
- Publish license tiers in the service catalog.
- After payment or entitlement creation, store the license through
POST /licenses. - Bind the license hash into quote terms, receipts, or attestations.
- Check the license before serving protected data.
Agent Flow
- Discover a service and inspect available rights.
- Pay through an allowed rail.
- Store the returned
license_hash. - Call
check_licenseover MCP before using the resource.
Check API
{
"license_hash": "0x...",
"agent": "0x1111111111111111111111111111111111111111",
"action": "commercial_output",
"context": {
"commercial": true,
"model_training": false,
"redistribution": false,
"derivative": true
}
}