Buy
Applications call a gateway over HTTP, handle a payment challenge, and receive results with receipts and evidence.
d402 turns HTTP 402 Payment Required into a distributed execution market. Applications make one structured request. Gateways route work to capable nodes. Validators check results. Settlement pays the wallets that earned the task. Anyone can define a new capability as a signed, versioned network object.
The site now follows the way people actually arrive: understand the protocol, buy from it, sell into it, or go deeper.
Applications call a gateway over HTTP, handle a payment challenge, and receive results with receipts and evidence.
d402-agent is the installable reference buyer: gateway discovery, capability search, spend policy, receipt cache, and signer plugins.
Nodes advertise capabilities, run bounded work, build reputation, and receive payment to self-managed wallets.
The protocol docs cover the API, payment rails, reputation, trust bundles, safety posture, and the whitepaper.
d402 scales beyond one service because capabilities are portable manifests, not hard-coded gateway features.
Capability authors publish manifests with input schema, output schema, determinism class, permissions, evidence, validators, pricing unit, and performance targets.
Signed registration envelopes bind manifest CIDs to wallet namespaces. Directory nodes index by capability ID, namespace, tags, validator, shard, and CID.
Gateways set policy: accepted manifests, trusted namespaces, non-deprecated versions, namespace proofs, schema compatibility, and exact CID pinning.
The first d402 capability fetches public pages, renders them when needed, extracts clean markdown with Defuddle, rejects blocked-page interstitials, and returns evidence for validation.
{
"status": "accepted",
"result": {
"title": "Example Domain",
"markdown": "# Example Domain\n\n...",
"contentHash": "sha256:...",
"evidence": {
"converter": "defuddle",
"snapshotterVersion": "playwright"
}
}
}
The implementation includes Base x402, Solana direct payment, task escrow, channel escrow, signed capability registrations, namespace proofs, trust passports, Sybil-aware reputation gates, and operator monitoring. Contracts and programs are not externally audited yet, so public deployments should cap balances and task sizes.