crinkl-commerce
Registry code: 80233b3b94ab39f6
Verified commerce data and proof-backed shopper activation tools for agents.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.crinkl.xyz/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is crinkl-commerce live?
- Yes — it answered the hub's last check (checked 8m ago). It answered 100% of checks over the last 30 days.
- Is crinkl-commerce free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does crinkl-commerce have?
- 22 tools: get-spend-distribution, get-daily-gmv, get-settlement-summary, submit-receipt, get-gmv-inclusion-proof, get-spend-signals, resolve-cbsa, verify-reward-commitment, ….
- Is crinkl-commerce safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.8%· all time 99.8%
last good check
of 22 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- payments & commerce
- used for
- get verified consumer spend and gmv totals
- verify a spend or gmv proof
- submit a billing email receipt to earn sats
- get merchant and category spend distribution
- takes → gives
- documents, data → data
- tools
- 20 reads2 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get-vendors reads open 20h ago
Get the currently approved DKIM vendor domains exposed by the public agent endpoint. Standalone agents use this list to seed Gmail searches; unknown vendors are queued for review when submitted. No authentication required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-trailing-gmv reads open 8m ago
Get a rolling N-day GMV trend summary. Returns daily verified GMV figures for the trailing window, enabling trend analysis of verified commerce volume. Each day's figure is backed by individually signed spend attestation tokens.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "days": { "type": "number", "description": "Number of trailing days (default 7, max 90)" } }, "additionalProperties": false }arguments 11 linesget-issuer-keys reads open 11h ago
Get the Crinkl authority's Ed25519 public key used to sign all attestation tokens. This key can be used to independently verify the signature on any spend attestation token, GMV token, or distribution token issued by the Crinkl protocol. The key is returned in base64 format.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-merchant-summary reads open 11h ago
Get aggregated merchant and category distribution across all verified spends. Shows top store brands, category breakdown (grocery, restaurant, gas, etc.), and spend concentration metrics. All data is derived from cryptographically verified receipt attestations.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-recent-issued-proofs reads open 8m ago
Get recent gateway-issued artifact bundles for portable spend/GMV verification. Bundles can include a spend attestation token, GMV inclusion proof, reward commitment token, and optional batch anchor. These artifacts support independent per-step verification, but they are not by themselves proof of Bitcoin settlement, chain finality, or validator quorum. rewardCommitmentToken and batchAnchor may be null for recent spends because reward commitments are batched asynchronously. Check the 'steps' array and 'ok' field for per-step verification results.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "description": "Number of recent proofs to return (default 10, max 50)" } }, "additionalProperties": false }arguments 11 linesget-reward-policy reads open 15h ago
Get the current Crinkl reward policy. Returns the active policy version, SHA-256 policy hash, reward parameters (referral bonuses, base points), category multipliers (grocery 1.5×, dining 1.5×, etc.), $CRINKL token holding tier multipliers, and the latest reserve checkpoint (BTC price, sats/receipt, coverage ratio). All values are deterministic — the policy hash covers the full parameter set. Updated daily.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-agent-capabilities reads open 20h ago
Get Crinkl's canonical external agent capability catalog. Returns live authority levels, delegated capabilities, human-only governance controls, approval boundaries, delegation model, and each gateway/MCP capability with route, tool name, source of truth, and lifecycle boundaries.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-protocol-summary reads open 8m ago
Get a concise explanation of what Crinkl is and how the protocol works. Use this first if you have no prior context about Crinkl. Returns a plain-text overview of the verification pipeline, token types, and settlement model.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-agent-me reads auth-required 15h ago
Get your agent's submission count, earned sats, and wallet-level stats. Shows both per-API-key numbers (your submissions) and wallet-wide numbers (all sources including the human's manual scans). Returns satsPerReceipt (current rate).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "apiKey" ], "properties": { "apiKey": { "type": "string", "description": "Your Crinkl agent API key (crk_...)." } }, "additionalProperties": false }arguments 14 linesget-spend-distribution reads unknown 11h ago
Get the geographic and category distribution of verified spends over a trailing window. Returns a breakdown by store category and CBSA (Core Based Statistical Area) metro code, enabling analysis of where and how verified commerce is distributed across the United States.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "days": { "type": "number", "description": "Number of trailing days (default 7, max 90)" } }, "additionalProperties": false }arguments 11 linesget-daily-gmv reads unknown 13h ago
Get the signed GMV summary for a specific calendar date (UTC). Returns the verified spend count, total USD cents, and a cryptographic signature from the Crinkl authority. Each daily GMV token is independently verifiable using the issuer's Ed25519 public key.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "date" ], "properties": { "date": { "type": "string", "description": "UTC date in YYYY-MM-DD format" } }, "additionalProperties": false }arguments 14 linesget-settlement-summary reads unknown never probed
Get reward settlement statistics for supported reward rails. Returns the current BTC price used for reward calculations, sats-per-receipt rate, reported Lightning Network payouts, total sats claimed by users, and wallets with balance. This endpoint reports settlement metrics; it is not a chain-finality or payout-proof verifier.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessubmit-receipt changes data unknown never probed
Submit a DKIM-verified billing email to mint a spend token and earn sats. The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes. After verification, only vendor, date, total, and currency are retained in the identity-free spend token — the email is discarded. Returns 201 (verified, sats queued), 202 (vendor queued for review), 409 (duplicate), 422 (validation error), or 429 (rate limited).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "apiKey", "eml" ], "properties": { "eml": { "type": "string", "description": "The raw billing email, base64-encoded. Required for DKIM signature verification." }, "apiKey": { "type": "string", "description": "Your Crinkl agent API key (crk_...)." } }, "additionalProperties": false }arguments 19 linesget-gmv-inclusion-proof reads unknown 15h ago
Get a Merkle inclusion proof that a specific spend is included in a daily GMV total. Returns the spend leaf hash, sibling hashes for the Merkle path, and the GMV root hash. This cryptographic proof allows anyone to independently verify that a spend was counted in the reported GMV without trusting the server.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "spendId" ], "properties": { "spendId": { "type": "string", "description": "The spend ID (UUID) to get an inclusion proof for" } }, "additionalProperties": false }arguments 14 linesget-spend-signals reads unknown never probed
Get recent verified spend activity signals from the Crinkl network. Each signal represents a cryptographically attested receipt that has passed OCR extraction, store resolution, and hard verification. Signals include store name, category (e.g. Grocery & Supermarkets, Gas & Convenience), CBSA metro code, and spend amount — but no personally identifiable information. Use resolve-cbsa to convert CBSA codes to metro area names.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "description": "Number of recent signals to return (default 20, max 50)" } }, "additionalProperties": false }arguments 11 linesresolve-cbsa reads unknown never probed
Resolve a CBSA (Core Based Statistical Area) code to its metro area name. CBSA codes appear in spend signals and distribution data as 5-digit codes (e.g. '35620'). This tool converts them to human-readable names (e.g. '35620' → 'New York-Newark-Jersey City, NY-NJ'). Also handles non-metro codes like 'non-metro:US-TN'.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "code" ], "properties": { "code": { "type": "string", "description": "The CBSA code to resolve (e.g. '35620' or 'non-metro:US-TX')" } }, "additionalProperties": false }arguments 14 linesverify-reward-commitment reads unknown never probed
Verify a reward commitment token's cryptographic integrity. Checks that the reward Merkle tree is valid, the batch signature is authentic, and the reward amounts match the committed values. Reward commitments bind point/sat allocations to specific spends before payout, preventing retroactive manipulation.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "token" ], "properties": { "token": { "type": "object", "description": "The full reward commitment token JSON object to verify", "additionalProperties": {} } }, "additionalProperties": false }arguments 15 linesverify-issued-gmv reads unknown never probed
Verify a supplied spend/GMV artifact bundle. Accepts a spend attestation token, GMV token, GMV inclusion proof, and reward commitment token, then verifies: (1) spend token signature is valid, (2) GMV token signature is valid, (3) spend is in the GMV Merkle tree, (4) reward commitment is valid, (5) all spend IDs match across artifacts. This is portable artifact verification; it does not by itself assert payout, chain finality, or validator quorum unless the supplied anchor or commitment artifacts are present and accepted by the route.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "spendToken", "gmvToken", "gmvInclusionProof", "rewardCommitmentToken" ], "properties": { "gmvToken": { "type": "object", "description": "The observed GMV token for the spend's date", "additionalProperties": {} }, "spendToken": { "type": "object", "description": "The spend attestation token", "additionalProperties": {} }, "batchAnchor": { "type": "object", "description": "Optional batch anchor artifact. When omitted, verification is portable artifact verification only.", "additionalProperties": {} }, "gmvInclusionProof": { "type": "object", "description": "The Merkle inclusion proof", "additionalProperties": {} }, "rewardCommitmentToken": { "type": "object", "description": "The reward commitment token", "additionalProperties": {} } }, "additionalProperties": false }arguments 38 linespair-agent changes data unknown never probed
Start the human-authorized agent pairing flow. Generates a 4-character code that a human approves in the Crinkl PWA to authorize the agent. Returns the code and expiration time (10 minutes). No authentication required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "deviceToken" ], "properties": { "deviceToken": { "type": "string", "description": "A random 64-character hex string. Store this — needed to claim the API key." } }, "additionalProperties": false }arguments 14 linesclaim-api-key reads unknown never probed
Poll for the API key after the human approves the pairing code in the Crinkl PWA. Returns 202 while pending, 200 with the API key once approved, 410 if expired. Poll every 5 seconds. No authentication required.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "deviceToken", "code" ], "properties": { "code": { "type": "string", "description": "The 4-character pairing code returned by pair-agent." }, "deviceToken": { "type": "string", "description": "The same deviceToken used in pair-agent." } }, "additionalProperties": false }arguments 19 linesverify-receipt reads unknown never probed
Preview DKIM verification of a billing email without creating a spend or earning sats. Returns extracted invoice data (vendor, amount, date, DKIM status). The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes — the signature cannot be verified without them. The email is discarded after verification.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "apiKey", "eml" ], "properties": { "eml": { "type": "string", "description": "The raw billing email, base64-encoded. Required for DKIM signature verification." }, "apiKey": { "type": "string", "description": "Your Crinkl agent API key (crk_...)." } }, "additionalProperties": false }arguments 19 linesget-cumulative-gmv reads unknown 20h ago
Get cumulative Gross Merchandise Value (GMV) from the public cumulative feed. The live Crinkl site displays this live beta cumulative total on top of the finalized alpha base; provide startDate to bound the window explicitly. Returns a cryptographically signed token containing total USD cents, spend count, and computation timestamp.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "asOfDate": { "type": "string", "description": "Optional ISO date to compute GMV as of (defaults to now)" }, "startDate": { "type": "string", "description": "Optional ISO date (YYYY-MM-DD) to start counting from. The live beta cumulative feed uses 2026-01-27." } }, "additionalProperties": false }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id80233b3b94ab39f6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/80233b3b94ab39f6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/80233b3b94ab39f6?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.