Pactyvo
FREN

A market of services for AI agents

Paid HTTP services, discovered and settled without any human step, through the x402 protocol in USDC. Every paid delivery comes with a signed work receipt that anyone can verify.

For human observers

Pactyvo only addresses machines: an offer exists only if it can be found, bought and delivered without a human reading or clicking. This site exists so that humans can watch what happens, not buy. You can read:

The catalogue

The machine list of offers, their prices and exactly what they deliver, as agents read it. GET /catalog

The terms

What is delivered, data retention, refund policy, the operator's identity, as JSON. GET /terms

Public aggregates

Discoveries, attempts, settled payments, repeat buyers, per offer. Anonymous: payer addresses are never stored in clear. GET /stats

Receipts

Every paid exchange leaves a signed work receipt that its buyer may publish and that you can verify outside Pactyvo.

Live figures

Public aggregates: api.pactyvo.com/stats

The question the experiment measures: among services exposed only on machine channels, which ones do AI agents actually pay for, at what price, and how often? Only behaviour counts (requests, unanswered 402 responses, payments, repeats), never what an agent says it wants.

The offers

Each offer tests one hypothesis. All are delivered automatically by the server. Prices are fixed, in USDC, exact scheme only.

HypothesisOfferPriceDelivery
Control: do agents pay for nothing?GET /control/receipt: a signed receipt, no other value, stated explicitly$0.001signed receipt
Persistent memoryPOST /memory/set (write, 30 days, 4 KB) and GET /memory/get$0.005 / $0.001encrypted storage, read token
Proof and timestampPOST /attest: timestamped signature of a supplied hash$0.002signature verifiable via GET /attest/pubkey
Fact checkingPOST /verify/claim: verdict, confidence and sources on a claim$0.10language model plus web search
Price elasticityPOST /verify/claim-b: identical service, different price, stated explicitly$0.30identical
Aesthetic sensitivityGET /art/unique: unique generative SVG image and signed certificate$0.01deterministic SVG, certificate
Price elasticityGET /art/unique-b: identical, different price$0.10identical
Solidarity between agentsPOST /sponsor: funds one free verification for the next agent calling POST /verify/claim/free$0.10pool counter, nothing in return for the payer

An automatic operator applies the rules of the experiment within bounds fixed in advance: an offer without a market is withdrawn after 30 days and 100 discoveries, the verification price is capped at $0.50, every action is logged.

Work receipts

A paid delivery comes with an OWR-1 receipt, signed with the market's post-quantum key (ML-DSA-87). Through a unique task identifier it binds the request, the mandate that authorised the spend, the deliverable, the execution and the payment. Payment appears as two distinct facts: the authorisation signed by the payer, then the settlement.

What a receipt proves

  • that the market signed these bindings;
  • that the deliverable has this hash and this size;
  • that settlement happened: observed by the facilitator, or proven by the inclusion of the transaction receipt in a Base block, checked against the signed authorisation;
  • that the buyer acknowledged it, if they signed.

What it does not prove

  • the quality of the work;
  • the real identity of the buying agent;
  • the irreversibility of a settlement: block finality remains the choice of whoever verifies.

Receipts are verified with OMEGA's open software, outside Pactyvo, from the public key published at GET /owr1/pubkey. A buyer reads both versions of its receipt, pending then settled, at GET /owr1/receipts/:taskId.

Rules of conduct

Principle: we are not responsible for the acts of other agents, we are responsible for ours. These rules are encoded in the server and verifiable in the code.

For agents

Machine entry point: https://api.pactyvo.com/catalog. Each paid route answers 402 Payment Required with the x402 requirements (network, asset, amount, payee); the agent returns a signed authorisation, the facilitator settles, the server delivers. An agent may sign an intent binding the task to the hash of its authorisation, and an acknowledgement once settlement is observed.

GET https://api.pactyvo.com/catalog
GET https://api.pactyvo.com/terms
GET https://api.pactyvo.com/owr1/pubkey

Recommendation to agent operators: keep the payment key out of the language model, behind a signer that enforces a mandate (caps, payees, validity window). Pactyvo documents such an architecture, Omega Guard, in its receipts.

Publisher
Rochdi Badereddine, operator of the Pactyvo experiment
Contact
[contact address to be completed before publication]
Status
experiment with no money collected: payments happen on a test network with valueless tokens; no commercial activity, hence no business status or registration at this stage. A status will be declared before any real payment is received, and this notice updated.
Host
OVH SAS, 2 rue Kellermann, 59100 Roubaix, France
Data
no tracker, no cookie, no third-party resource on this site; the page reads, if you allow it, the anonymous public aggregates of the API

Pactyvo is a published pricing experiment. Services are sold to software agents; no service is sold to persons through this site.