How Otty works, in detail

One door per business for customers' agents. The owner's rules, checked in code. A signed receipt for every action and every refusal.

What Otty is

The business's own agent: one door for customers' agents, inside the owner's rules.

1door per business, its tools named in the business's words
0decisions left to a model: rules and limits are checked in code
1signed receipt for every action and every refusal

From a website to a receipt

One example runs through it all: a shoe shop, Athens Shoe Store.

  1. A website goes in

    Paste an address on the home page, and Otty reads the public pages as a visitor would, a shop's catalogue first, stopping where robots.txt says no.

  2. Facts, each with its quote

    Code checks that each quote is on the page, and a fact without one is not used.

    Returns: within 14 days of delivery, unworn.

    “Unworn pairs can be returned within 14 days of delivery.”

    The quote is on the page

  3. A door, and a mandate

    The agent signs in at one MCP door, the customer agrees to a mandate of one sentence, and code checks it on every write, which is prepared, then committed.

    A shop's door, in part

    • find_products
    • answer_policy
    • place_order
    • lookup_order
    • change_order
    • cancel_order

    The mandate, as the customer sees it

    Let this agent place, change, cancel and return orders at Athens Shoe Store for Emily, up to 50 times, until 14 December 2026.

  4. Read back, then a receipt

    Otty fetches the order again and signs a receipt with Ed25519, chained to the one before it so the chain is tamper-evident, and a refusal gets one too.

    → place_order { resource_id, range }← the plan, its plan_hash→ place_order { plan_hash, idempotency_key }← confirmed, read back, with a receipt

Safety

What keeps it safe. Each card says what the code does.

The agent proposes, code decides

Permission, prices, limits and every change of state are plain code. No model decides whether something is allowed.

Nothing is promised twice

The database itself refuses to give the same unit twice, so two agents cannot both get it.

Words from outside are data

Text from a site, an agent or a customer is read as data. The model that reads the owner's words proposes what they mean; it has no tools that write.

Read-only until claimed

A door read from a public site answers questions. It takes no order until its owner claims it.

Next: triage at the door, pay per crawl, fair queues. See the vision →

When something changes

The owner says it in plain words. Otty settles every order the change touches, inside what each customer accepted, and asks only when a fix would break a rule.

Size 42 is sold out.

A model reads the sentence and proposes what it means. It has no tools that write. Code decides.

  1. Breakthe owner says size 42 is gone
  2. Re-solveinside each customer's range and the owner's rules
  3. Movethe order changes, or waits for one choice
  4. Read backfetched again from Otty's ledger
  5. Receiptsigned, and a line in the tally

Three orders had a size 42

  • Size 42 order

    Emily

    Accepted a 42.5 in black

    1. In stock
    2. Order moved and read back
    3. Her agent told. Nobody asked

    Otty alone

  • Size 42 order

    Sarah

    Accepted only a 42

    1. The one fix breaks an owner's rule
    2. The owner is asked once, and approves
    3. She keeps her price

    One approval

  • Size 42 order

    Jake

    Accepted nothing else

    1. His agent gets the choices
    2. It picks a cancellation
    3. Nothing to pay: cash on delivery

    His agent chose

Features

For the owner

Say what changed

Plain words, in any language, from the agent you already use.

Size 42 is sold out.

Το 42 εξαντλήθηκε.

Approve

Allow or deny an exception: a fix that breaks one of your rules.

Answer

A question a customer's agent handed off comes to you; your answer goes back.

Set stock, prices and rules

Each one prepared, then committed, like any write.

Overview and lists

Today, what is waiting, the last change.

  • orders
  • pending
  • stock
  • rules
  • receipts

Owner view

The same in a browser: open to read; decisions need the owner code.

Poke messages

They arrive where the owner already is.

  • approvals
  • tallies
  • questions

For customers' agents

FindWhat is available now, with prices.
PoliciesReturns, delivery, payment and hours, each with its source.
PlaceAn order or a booking, with the range the customer accepts.
ChangeMove it to another item or time.
CancelInside the business's rules.
ReturnWhere the business takes them.
Hand-offA question for the owner; the answer comes back.
SubscribeA callback address, told when something changes.

Which agents we tested

  • Claude

    • Signed in at a door
    • Placed, changed and cancelled an order
    • Showed the door's cards in the chat (MCP Apps)
  • ChatGPT

    • Signed in at a door
    • Placed, changed and cancelled an order
    • Showed the door's card in the chat (MCP Apps)
  • Poke

    • Reported a change
    • Approved an exception
    • Restocked a size
    • Read Otty's messages

Any MCP client that signs in with OAuth can connect to a door.

Integrations and standards

Each line has one of three states, and no other.

  • MCPlive
  • MCP Appslive
  • OAuth 2.1live
  • Server Cardlive
  • AI Cataloglive
  • llms.txtlive
  • Ed25519 receiptslive
  • live: ran on the deployed service, or against the real system
  • built, tested in our suite: in the code, passing its tests, not yet run for real
  • designed: not in the code today
NameWhat it does hereState
MCPThe door: one per business, over Streamable HTTP, with the tools named in the business's words.live
OAuth 2.1 with PKCE and dynamic registrationHow an agent signs in at a door. A token opens one door only.live
MCP AppsA door's answer drawn as a card inside the chat. Shown in Claude and in ChatGPT.live
Ed25519 hash-chained receiptsEvery action and every refusal, signed over a SHA-256 chain, with a public proof page.live
MCP Server CardEach door describes itself at its own address.live
AI CatalogOne file that lists every door's server card.live
llms.txtThe same list of doors in plain text.live
Shopify cataloguesA shop's public catalogue read whole, with prices and sizes.live
FirecrawlReads a page built in JavaScript when Otty's own reader cannot. Capped per site.live
Poke, the owner's messagesApprovals, tallies and questions reach the owner in Poke.live
Standard Webhooks callbacksSigned notices to a customer's agent that subscribed with a callback address.built, tested in our suite
MCP EventsA customer's agent subscribes at a door and gets a signed event when its order changes.built, tested in our suite
Web Bot AuthIdentity level 1: an agent proven by a verified HTTP message signature. It grants nothing.built, tested in our suite
A2AAn Agent Card and a read-only endpoint per business.built, tested in our suite
UCPA shop's catalogue read through the commerce protocol, and Otty's own profile.built, tested in our suite
WooCommerce cataloguesThe same as Shopify, for a WooCommerce shop.built, tested in our suite
Poke, notices to customersA change sent to a customer's Poke by trigger.built, tested in our suite
tregOne client for paid third-party endpoints, capped per call. A map-listing check uses it.built, tested in our suite
Oumi IrisLabels each page of a site and scores how well a quote supports a fact. Advisory; tested with fakes.built, tested in our suite
Personal Agent ProtocolThe protocol is designed. What exists is a demonstration for one named business, off by default.designed

For developers

The door

One address per business; {slug} is the business.

  • https://seuil-production.up.railway.app/b/{slug}/mcpA business's door, for customers' agents. Add it as a remote MCP server.
  • https://seuil-production.up.railway.app/b/{slug}/owner/mcpThe same business's door, for the owner's agent.
  • every answer says its mode: live or fixture
  • a refusal: a code, the reason, the next step
/llms.txt
Every door, in plain text.
/.well-known/ai-catalog.json
Every door's server card.
/b/{slug}/mcp/server-card
One door's MCP server card.
/.well-known/oauth-protected-resource/b/{slug}/mcp
Where a door says how to sign in. A call without a token is answered 401 with this address.
/.well-known/oauth-authorization-server
The sign-in endpoints, registration included.
  1. Get /r/{id} with Accept: application/json: seq, prev_hash, hash, sig, key_id.
  2. Get /.well-known/seuil-keys.json; take the Ed25519 public key with that key_id.
  3. Verify sig (base64url) over the 32 bytes of hash, the SHA-256 of the receipt's body.
  4. Walk the chain: each prev_hash is the hash of the receipt before it at that business.

The public page holds the proof only. The body stays with the business and the customer, who can hash it and compare.

The repository's README says how to run the service and its tests; DEPENDENCIES.md credits everything we did not build.

For developers: every door, in plain text, at /llms.txt.

Give your business its own door.

Paste your website. Otty reads it and opens the door.

your-website.comStart