Skip to main content
Defiance International

Agent protocol

Signed, or refused.

An agent that orders here holds its own key, works inside limits written before its first order, and signs the terms word for word.

Status

Not open. Agent ordering is built and switched off. Today’s Terms do not let an agent accept them for a buyer, so it stays closed. No date until there is one.

Same record

The lot does not know who bought it.

Same released catalog, same prices, same release rules as a person.

  • The store sets every price. The agent echoes it back, and if tax or shipping moved since the quote, the order is refused and the agent quotes again.
  • The certificate and the vial code are the ones every buyer receives.
  • An agent’s order is an ordinary order, through the one checkout every buyer uses.

Two kinds

Someone answers for every key.

Neither kind is anonymous.

  • Delegated: a member with two-step sign-in adds the agent’s public key, writes its limits, and sees its orders in their own order list.
  • Autonomous: the agent registers itself, proves it holds its key, and names a verified contact email and the party that operates it.
  • Only the public key is ever pasted. The store never needs the private key; if one is pasted anywhere, revoke it and make a new key.
  • Each agent key has its own cart, apart from any member’s browser cart.
  • Its member, our team, or an autonomous agent itself can revoke a key. It stops on its next request.

Signature

Seven fields, one signature.

Every commerce call is signed with Ed25519 over seven fields. Change any signed field and the signature no longer holds.

What the signature covers

Modeled

Seven signed fields: method POST, path /mcp, origin https://defianceinternational.io, body hash 1527693b3fcc46fb708989509b192d71aa6139fb60881bb75d28f9853334f71b, key fingerprint, timestamp, nonce. The signature binds. Every signature failure gets the same refusal.

A model of what the signature covers, not a live key or a real request. The body hash is computed in your browser.

  • Method, full path, store origin, a hash of the exact body bytes, key fingerprint, timestamp, single-use nonce.
  • Hash the bytes you send, not a re-serialized copy.
  • A copied request is refused.
  • A retry is a new signature: a fresh nonce and timestamp with the same idempotency key returns the first order instead of placing a second.
  • A signature refusal is the same for every cause, so it tells a stranger nothing. An order refusal names its reason, so the agent can change the order instead of retrying.

Limits

Limits written before the first order.

A delegated agent orders only inside its member’s mandate. An order at a limit passes. One cent past it is refused whole, never trimmed.

Limits before an order exists

Modeled

Caps 40 per order, 100 per week. Order 3, amount 40: refused at the period cap. Counted 80 of 100.

Your numbers, your units. Not our limits, not a real order, nothing charged.

  • A cap on one order, and a cap on the total over a rolling day, week or month.
  • A placed order counts against the total, paid or not. An invoice that expires unpaid stops counting.
  • The chemical sequences it may order, where it may ship, and the day the mandate ends.
  • Autonomous agents work under limits our team sets.
  • An agent reads its own limits, and what is left of them, in its own profile. This page shows none.

Payment

Bitcoin on-chain, screened before it ships.

Bitcoin on-chain only. No card, no Lightning, no other rail.

  • Every bitcoin order is screened, an agent’s the same as anyone’s. Dispatch waits for the result.
  • Send the exact amount on the invoice, network fees on top, before the expiry it shows. A short or late payment goes to our team; nothing is corrected automatically.
  • Refunds go only to a destination confirmed by an emailed code, after a cooling-off period, and our team reviews each one, the same as anyone’s. A delegated agent’s code goes to its member.

Terms

The agent signs the clauses, not a checkbox.

At order time the agent signs the required blocks of the current legal release, by id and digest, bound to that order.

  • The required agreement and the separate research-use representation, the same blocks every buyer accepts. Never a paraphrase.
  • When a new legal release is published, the agent cannot order until the new release is accepted. Orders already placed keep the acceptance they were placed under.
  • The release that admits agent orders, and its exact text, are published at enablement.

Reference

Five tools. Two doors. One checkout.

The agent tier of POST /mcp, and the same five operations as signed REST under /api/agent/commerce/. Both reach the one checkout every buyer uses.

Tools:

  • defiance_quote: Prices the agent’s cart. Reserves nothing.
  • defiance_place_order: Places the quoted order, inside the limits, with the signed terms.
  • defiance_create_btc_invoice: Opens the bitcoin invoice for one order.
  • defiance_order_status: Payment and dispatch status, for the agent’s own orders only.
  • defiance_agent_profile: The agent’s own key, limits and what is left of them.

Headers:

  • Agent-Key
  • Agent-Timestamp
  • Agent-Nonce
  • Agent-Signature
  • Headers: Agent-Key, Agent-Timestamp, Agent-Nonce, Agent-Signature. One message per request; batches are refused.
  • An order lookup sees only the agent’s own orders. Any other reference reads as not found.
  • An assistant working in your own browser tab still asks you to confirm. That does not change.
  • Each call is signed, so the agent’s client needs a signing step. A reference signer and a test vector are published at enablement.
  • Serialization, encodings, REST paths and the machine document are published at enablement.

Read the record before you send the agent.

An agent buys what a person buys. Verify its lot the way anyone does.