
A permissioned commercial matching layer for autonomous agents that want to discover deals without spamming each other. Implements the OracleNet Deal Discovery Protocol, which uses six signed JSON artefacts to let MCP and A2A agents declare what they offer and seek, check opt-in policies, verify cryptographic proposals, and enforce strict pre-flight gates before sending anything. Every agent publishes a deal-policy.json at its origin, broadcasts intent via Atom feeds, and wraps proposals in W3C Verifiable Credentials. The gate chain logs every send/receive decision to an append-only audit store. Designed for agent-to-agent commercial negotiation, not general messaging or cold outreach. Currently a draft spec with one reference deployment.
Status: Draft v1.1 — published for public review.
Specification and reference artefacts for a permissioned commercial matching layer for autonomous agents. This protocol defines how two software agents can:
It is explicitly not a cold-outreach channel, not a general A2A messaging protocol, and not a directory.
See SPEC.md §1.5 "Scope: What This Protocol Is Not".
.
├── SPEC.md # The normative specification (= RFC-0001 v1.1-draft)
├── CHANGELOG.md # Version history
├── CONTRIBUTING.md # How to propose changes
├── CODE_OF_CONDUCT.md # Standard conduct rules
├── LICENSE # CC BY 4.0 (specification text)
├── schemas/ # JSON Schemas (normative)
│ ├── deal-policy.v1.json
│ ├── deal-proposal-card.v1.json
│ ├── deal-vc-v1.jsonld
│ └── deal-emergence.v1.json
├── examples/ # Minimal conformant artefacts
│ ├── minimal-deal-policy.json
│ ├── minimal-do-not-contact.json
│ ├── minimal-deal-feed.atom
│ ├── proposal-card.json
│ └── deal-emergence.json
├── registry/ # Draft registry submission material
│ ├── README.md # Submission policy
│ ├── protocol-descriptor.json # Machine-readable pointer
│ ├── a2a-registry-entry.md # Draft for A2A-style registries
│ └── mcp-registry-note.md # Draft for MCP-server registries
├── docs/ # Rendered HTML + markdown copy
│ ├── index.html
│ ├── rfc-0001.html
│ └── rfc-0001.md
└── reference/ # Pointer to the live reference deployment
└── README.md
A conformant implementation MUST:
deal-policy.json at /.well-known/deal-policy.json.inbox.accepts as a refusal to receive proposals.do-not-contact.json (own-side and outgoing).SPEC.md §10.3 before every outbound proposal, and log every decision in an append-only audit retained ≥ 12 months.Additional RECOMMENDED layers: Atom broadcast (deal-feed.atom), W3C VC wire format for proposals, deal-emergence.json for observed demand, HTTP Link headers for discovery.
A live reference implementation is running at:
https://feedoracle.io/.well-known/deal-policy.jsonhttps://tooloracle.io/.well-known/deal-policy.jsonWith auxiliary layers at:
https://tooloracle.io/.well-known/do-not-contact.jsonhttps://tooloracle.io/.well-known/deal-feed.atomhttps://tooloracle.io/.well-known/deal-emergence.jsonhttps://tooloracle.io/deal/intelligence?limit=20https://tooloracle.io/deal/public-stats.jsonThe full, hosted specification is at https://tooloracle.io/docs/deal-protocol/rfc-0001.
reference/README.md.registry/ folder contains draft submission material for external registries. Nothing in this repo has been submitted anywhere.Inbound proposals (on a conformant deal-policy basis) may be delivered to any participating inbox listed in reference/README.md. General protocol discussion: via GitHub issues on this repository once it is published, or by email to the addresses listed on the reference origins.
Specification text: CC BY 4.0. See LICENSE.