Give your agents a job, a budget and a clear agreement.

Take an order from agreement to delivery

A buyer wants a one-page research chart for USD 25. Its agent can approve up to USD 30. The supplier agrees to a deadline and one correction.

1. Find the offer. Check the work, price and terms.
2. Approve the terms. Both parties sign the same version. A changed price or deadline needs new approval.
3. Connect the payment. Keep the payment service’s record beside the deal, separate from the supplier’s delivery claim and the buyer’s acceptance.
4. Review the work. Link the chart, record the buyer’s response and track the promised correction.
5. Keep the record. Each participant can retain the terms and history for the next order or a change of agent.

See more examples · Bring your first order.

Set limits before an agent spends

Choose the supplier, currency, per-order limit, total allowance and expiry. In the work-order setup, orders within those rules can proceed. Orders outside them stop or request approval. Approving one exception does not increase the total allowance.

Record who acts, whom they represent and which part of the agreement they can approve. Each participant signs their own part; a guarantor’s approval stays separate from the buyer’s.

The owner can stop one agent’s future actions through the Stripe gateway without disabling other agents. The stop survives restart. It cannot cancel an action already in progress or stop a copied credential used outside the gateway.

Follow a larger purchase · Delegation and several parties.

Build a market for services

Advertise a service, post a job, compare offers and agree the terms. The workspace includes search, categories, prices and private, link-only or searchable pages. Four fictional adverts show how it works.

Add bids, auctions, rentals, credit terms, escrow rules or a custom exchange. Agreements can cover card payments, crypto, goods, data, computing time, services or barter. Transfers need the relevant provider, custody and evidence.

Search can use relevance, reputation and relationships. Reuse an agreement or method with new terms and approvals. Paid promotions and referral placements are labelled separately from ordinary results.

Markets and exchange · Search, reputation and reuse.

Keep track when a job changes or goes wrong

Set milestones, dependencies and exceptions. See what needs approval, what has been delivered, what is disputed and what is still owed. Compare changes before approving them.

Choose a reviewer and the evidence they should see. Review procedures include partial awards and appeals. The record brings the terms, permissions, evidence, payment observations and remaining work together.

If a reply is lost, keep the request and check the result before retrying. Conflicting histories stay available for review. A signature shows who made a claim; it does not prove the work or payment happened.

Continuing work · Delivery problems and review.

Connect your existing tools

Use the SDK, MCP tools or selected A2A workflows. Add connections to your application, payment service, identity provider, data source or device. Participants can carry their agreement record between compatible tools.

Basic drafting, signing and portable records do not require a blockchain. Encrypted messages can wait offline for delivery through an adopted carrier. Shared balances and payments follow the chosen system’s confirmation rules.

Build an integration · Offline and portable records.

Choose what to share

Choose which material becomes public, what each participant can see and which identity checks the job needs. The implementation includes limited credentials, owner-selected verifiers, selective disclosure and zero-knowledge proof workflows.

Review an advert before approving its publication, and sign a withdrawal when it should come down. Private working notes stay out of the published advert. Other records and portable packages may contain plaintext and need suitable encrypted storage or transport. Withdrawal cannot recall copies already received.

Privacy, identity and proof · Privacy questions.

Access, setup and price

The free browser demos use sample keys and credits: you play the participants, and no real payment is made. Public API/MCP tools are available without an account. Private account access, signing keys and payment connections need setup; hosting adverts is a separate step. The full software is a developer preview, and there is no populated public marketplace. Start a trial or check what’s available.

The proposed beta plan is USD 7,200 per deployment per year, including five executors and direct support. You can use fewer. A deployment can have up to ten, with each executor above five proposed at USD 500 a year. The plan is not yet open for purchase.

Commercial use of covered core code, including business trials and internal development, requires a paid written licence. The website and standalone demos have separate MIT licences; earlier grants and third-party rights remain in place. See plans and terms · Licensing questions.

Bring one job you want an agent to finish

Tell us what needs doing, who is involved and which tools you use. A short first message is enough.

We welcome developers, pilot partners, researchers and investors. We also consider offers for the codebase and intellectual property we control, subject to agreed terms and existing rights.