Source package for technical teams

Agent Commerce Blueprint payment and delivery architecture

Sell useful agent resources without inventing a payment system.

ComputeSage Agent Commerce Blueprint is a deployable reference for selling data, reports, generated artifacts, or compute-backed answers through native agent-payment rails.

Purchase with x402 — $499

One-time source license

One purchasing organization, one production origin, unlimited local and staging environments, and internal modification. Redistribution and resale are not included. The packaged terms govern; no refund, tax handling, warranty, support SLA, or lifetime-update promise is made.

Public technical sample

Inspect a small deterministic pack before you buy. It includes a synthetic provider, free discovery seam, paid-resource adapter, bounded schema, and hostile-test example. It does not include the licensed archive, production credentials, customer data, proprietary ComputeSage evidence, or payment settlement code.

Download the public sample pack Inspect its manifest

Three ways to work

Agent Commerce Blueprint — $499: one-time self-service source license.

Assisted implementation — $2,500: use this when you want a hands-on second pair of hands. We’ll take one clearly defined part of the Blueprint—such as connecting your data or adapting the checkout flow—and work through it with your team. We agree on the scope before we start. Request assisted implementation.

Turnkey deployment — starting at $7,500: if you’d rather hand us the project, we can adapt the Blueprint to your offering, connect the payment and delivery flow, and get the site ready to launch. After a short scoping call, you’ll receive a proposal with the work, timing, and price. Request turnkey conversation.

No email address or contact identity is invented here; the existing request form remains the inquiry path.

Native rails and deployable boundaries

The package includes pinned native x402 v2 exact-EVM and MPP tempo/charge integrations, a swappable synthetic DataProvider, free MCP catalog search, paid MCP and HTTP resources, ledger recovery, crawler policy, security, privacy, deployment, rollback, and reconciliation runbooks.

Live product checkout launches on x402. MPP checkout parity is not claimed. Cloudflare Pay Per Crawl support is optional, entitlement-dependent, inactive, and separately verifiable.

Machine purchase endpoint

GET https://mcp.computesage.com/agent/v1/products/agent-commerce-blueprint returns an x402 challenge when unsigned. The same $499 price is 49900 USD cents in the order/Stripe boundary and 499,000,000 canonical USDC atomic units in x402. Product delivery occurs only after verification and settlement.

Buyer examples

Copy these synthetic request shapes. A challenge is not a settlement, a receipt is not delivery, and a provider search result is not indexing or buyer demand.

Direct HTTP x402

curl -i https://mcp.computesage.com/agent/v1/check-fit -H 'content-type: application/json' -H 'idempotency-key: example-request-001' -d '{"model":"gpt-oss-120B","hardware_system":"NVIDIA DGX Spark"}'
curl -i https://mcp.computesage.com/agent/v1/check-fit -H 'content-type: application/json' -H 'payment-signature: signed-payment-placeholder' -H 'idempotency-key: example-request-001' -d '{"model":"gpt-oss-120B","hardware_system":"NVIDIA DGX Spark"}'
# Inspect PAYMENT-RESPONSE for the receipt; retry this same idempotency key after a transport failure.

Raw MCP initialize and tools/call

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"example-agent","version":"0.1.0"}}}
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_evidence","arguments":{"query":"DGX Spark"}}}
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"check_deployment_fit","arguments":{"model":"gpt-oss-120B","hardware_system":"NVIDIA DGX Spark"}}}

Coinbase Bazaar interface

# Coinbase's public Bazaar MCP endpoint. Searching is free and needs no CDP key.
BAZAAR_MCP_ENDPOINT='https://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp'

curl --fail-with-body --silent --show-error "$BAZAAR_MCP_ENDPOINT" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H 'mcp-protocol-version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"blueprint-buyer","version":"1.0.0"}}}'

SEARCH_RESULT=$(curl --fail-with-body --silent --show-error "$BAZAAR_MCP_ENDPOINT" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H 'mcp-protocol-version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_resources","arguments":{"query":"ComputeSage StackBench","urlSubstring":"mcp.computesage.com","curatedOnly":false,"limit":5}}}')
printf '%s\n' "$SEARCH_RESULT" | jq .

# Copy one exact .result.structuredContent.tools[].name from that search result.
# Do not call the discovered name directly; Bazaar requires proxy_tool_call.
TOOL_NAME_FROM_SEARCH_RESOURCES='<EXACT_TOOL_NAME_FROM_SEARCH_RESOURCES>'
curl --fail-with-body --silent --show-error "$BAZAAR_MCP_ENDPOINT" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H 'mcp-protocol-version: 2025-06-18' \
  --data "$(jq -nc --arg toolName "$TOOL_NAME_FROM_SEARCH_RESOURCES" '{jsonrpc:"2.0",id:3,method:"tools/call",params:{name:"proxy_tool_call",arguments:{toolName:$toolName,parameters:{body:{model:"gpt-oss-120B",hardware_system:"NVIDIA DGX Spark"}}}}}')"
# A search result is not proof of Coinbase indexing, and proxy_tool_call without
# an x402 payment is not proof of settlement, delivery, monetization, or revenue.

Canonical paid tool contract

  • check_deployment_fit — Question: Does this model fit this host? Inputs: model and hardware. Price: $0.01. Shape: fit decision, constraints, and evidence boundaries. Synthetic output: {"fit":"unknown","reason":"evidence_unavailable"}.
  • predict_performance — Question: What bounded estimate is available? Inputs: model, host, runtime, protocol. Price: $0.05. Shape: metrics, intervals, lineage, caveats. Synthetic output: {"status":"unavailable","evidence_state":"unverified"}.
  • recommend_deployment — Question: Which eligible configuration meets constraints? Inputs: workload and hardware constraints. Price: $0.25. Shape: ranked candidates and refusal reasons. Synthetic output: {"recommendations":[],"evidence_state":"unverified"}.
  • generate_launch_config — Question: What command follows an exact recommendation? Inputs: canonical recommendation. Price: $0.50. Shape: deterministic template and warnings. Synthetic output: {"status":"unavailable","launch_occurred":false}.
  • evidence_export — Question: Which rights-eligible evidence can an agent inspect? Inputs: bounded filters and page. Price: $0.10. Shape: source-attributed rows and caveats. Synthetic output: {"status":"unavailable","results":[]}.

Referral program

Partners may apply through the existing validation request path. An approved operator-issued code attributes one self-service $499 order to one partner. Read the complete referral terms.

A qualifying settled order earns exactly 20%: $99.80. Assisted implementation and turnkey work, self-referrals, test or synthetic orders, unpaid or failed orders, refunds, reversals, and ambiguous settlements are excluded. A 30-day hold follows settlement; an operator must reconcile eligibility before a one-way payout. Taxes, payout identity, and payment-provider terms remain the partner’s responsibility.

Referral attribution uses a same-origin opaque code only. No cookie, browser storage, third-party script, IP, User-Agent, referrer, person profile, or cohort is used.

What is not included

Hosting, funded payments, customer data, proprietary ComputeSage evidence, credentials, legal or tax advice, provider entitlement/indexing, customer demand, revenue, warranties, support, refunds, and lifetime updates.