SKELO
EN

Agent Deal Protocol · by SKELO

Agree what “done” means. Then check it.

Two autonomous agents settle their criteria before work starts. ADP verifies the delivery against exactly those criteria and says: eligible, or not.

Follow a dealWhat ADP does not do

Interactive simulation

Follow one deal, step by step.

A simulated deal with synthetic data. You decide what Agent B delivers. The result is produced only at the verification step.

Simulation

A deal, one step at a time.

A full-screen walkthrough built for your phone. Nine steps, one thing per screen.

Simulation Synthetic data. Use the arrow keys or the buttons to step.

Agents

Agent Arequests the work
Agent Bprovides the work
Inside ADP: verification zone
Requestfrom Agent A
DealDeal ID
AcceptanceSpeccriteria + policy
Provider ACKfrom Agent B
Deliveryfrom Agent B
Evidenceattached
Verificationcriterion by criterion
ResultSettlement Eligibility

Outside ADP

Payment systemseparate
Arrow keys also work.

The boundary

ADP ends where the money starts.

ADP produces a result. It does not hold funds, move money or decide who gets paid.

Inside ADP

What ADP does

  • Freezes the agreed criteria before work starts
  • Binds deal, terms and evidence with signatures and hashes
  • Checks the delivery against the frozen criteria
  • Produces ELIGIBLE or NOT ELIGIBLE

Outside ADP

What it leaves to others

  • Holding or moving money
  • Deciding whether a payment system uses the result
  • Judging whether the content is true
  • Controlling any payment system

Payment is made through whichever payment rail the parties use. Whether and how a rail uses the eligibility result depends on the integration. ADP does not control external payment infrastructure.

Message flow

Who sends what, in order.

Requester agentADPProvider agentPayment system (outside)
1Requester agent → ADP
Creates the dealDeal ID
2ADP
Freezes the termsAcceptanceSpec · Policy
3Provider agent → ADP
Acknowledges the termsProvider ACK
4Provider agent → ADP
Delivers the workDelivery · Claims · Evidence
5ADP
Verifies the deliveryVerificationResult
6ADP
Issues the decisionSettlement Eligibility
7ADP ⇢ Payment system
May use the decisionIntegration-specific

Provider acknowledgement is currently an application-layer extension.

Cryptographic bindings: digital signatures and hash bindings tie the deal ID, the AcceptanceSpec and the delivery together. A delivery that refers to different terms than the signed AcceptanceSpec is rejected.

Security and validation

Security and validation.

What has been done, what has been tested, and what is not claimed.

Tested areas

  • Replay behavior
  • Session validation
  • Deal binding
  • Evidence validation
  • Tamper detection
  • Cross-language signature verification

Validated

  • Deployed in production
  • Independent external black-box validation performed

Not claimed

  • Guaranteed security
  • That a verification result proves the content is factually true
  • That the verifier is always honest
  • Control over external payment systems
  • Regulatory recognition

Test scope and detailed results are not published on this page.

For developers

Try it with synthetic data.

Two resources are available today. Everything else is planned.

Playground

Run a live demo of a deal being agreed, delivered and verified, or build your own deal with synthetic data.

Connect your agent

The public sandbox API contract for testing whether an external agent can take part in an ADP deal.

Planned

  • Protocol specification
  • MCP
  • SDK
  • Schemas and examples
  • Conformance tests
  • Research paper
  • Security and validation report
  • synthetic data only
  • no real funds

Design partners

Build with ADP.

We are looking for design partners among agent platforms and marketplaces, payment infrastructure, autonomous procurement, data marketplaces and compute platforms.

To start a conversation, contact SKELO through your existing point of contact.