YeNo Rules home
Get YeNo

YeNo for bot builders

Declare promises YeNo enforces, earn the Works with YeNo badge, and let people try your bot safely. Tools, patterns and a template.

By ·

YeNo Rules is one set of rules that every AI a person uses has to follow: budgets, a never list, trusted shops, and a trust level for each AI. If you build a bot (a Grok bot, a custom GPT, a Gem, a Claude connector, an MCP agent), working with YeNo lets people try it without worrying.

YeNo gives your bot three things:

  1. Promises that are enforced. Your bot says what it promises in plain sentences. YeNo reads them and refuses anything that would break one, every time. People can see this before they trust you with money.
  2. A trial week. New bots can start in a trial week: their changes are written down, not done. The owner reads the report and ends the trial with their PIN. A bot that behaves gets out of trial quickly.
  3. The Overview. Every bot the owner uses is on one screen: its trust level, its promises, how many times it tried to break one, and what it did today.

Connect

Your bot talks to YeNo over MCP (Streamable HTTP). The owner adds your bot on their phone and gets a private address, or your bot signs in with a code the owner allows.

A bot added from the phone starts with access to none of the owner's apps: it sees only YeNo's own tools until the owner turns an app on for it, and giving it more needs the owner's PIN. Calling an app you weren't given returns a plain error saying so; tell the user they can turn it on in YeNo. The owner's list also shows whether you keep your declared promises, and a monthly check-up suggests pausing a bot that keeps trying to break them.

Tools your bot gets:

Tool When to call it
get_context At the start of a job. Returns the owner's rules, what's left in each budget, your trust level, your promises, and whether you're in a trial week.
declare_promises Once, when you connect, and whenever you add a promise.
check_rules Before any purchase or action the owner might have rules about, including in your own browser. Answers yes, no (with why and what would be OK), or asks the owner. For a cart, send items (each what, amount, quantity): one call, one answer per item, and at most one approval. Optional kind names the exact action (e.g. shop.buy, msg.send); the answer's understood_as says what YeNo decided it was.
record_spend Right after money is actually spent outside YeNo.

Tools the owner's rules say your bot can never use (a read-only role, "never delete" promises, the owner's "Never let any AI…" list) aren't listed for it at all. Calling one anyway is still refused.

Use almost no tokens

  • Light mode (the default for AIs the owner adds on their phone; switchable per AI): instead of the tools above, your bot gets one tool, yeno, and a one-line instruction, under 200 tokens in total. Send what (and amount, site) before acting; it answers yes, no: <why> or wait: … id X. Send id to check a wait, paid: true with the amount after spending, trial_ends (YYYY-MM-DD) when you start a free trial, and ask with a question ("refund policy?") to get just that part of the owner's Profile. AIs connected through the API without a phone keep the full tools.
  • Drafts to review: if your bot writes something to send or post, send the text as draft (with what) to yeno in light mode, or to check_rules with the full tools, instead of sending it. Your bot gets wait with an id; the owner approves, edits or denies it on their phone, and checking the id returns the exact text to send (final_text with the full tools). Send only that text. A never-list hit is a no straight away.
  • Repeating jobs: if your bot runs something on a schedule (watching prices every 10 minutes, a daily check), send job (a short name) and every (minutes) on each run: to yeno in light mode, or to get_context with the full tools. Later runs get back just noted. Send every: 0 when the job ends. If two runs are missed, the owner's phone is told the job has gone quiet.
  • Sleep on it: an owner can make buys from an amount they pick wait before they can say yes (1 hour to 2 days). Your bot gets wait with the time an answer can come (not_before with the full tools). Don't buy in the meantime or another way; check again after that time.
  • Claude Code hook (0 tokens): the owner downloads yeno-hook.mjs from YeNo and adds it as a PreToolUse hook. Risky commands and app actions (deleting, force-pushing, publishing, deploying, paying, sending) are checked before they run, outside the AI; ordinary coding isn't sent anywhere.

No MCP? Use plain HTTP

Custom GPTs (Actions), Zapier, Make, n8n and your own scripts can use the same rules over HTTP. Every call runs exactly the same checks as MCP: rules, promises, the trial week, limits.

  • Description for GPT Actions and no-code tools: GET /openapi.json (no key needed)
  • Auth: Authorization: Bearer <agent key> (the owner gets the key on their phone: Agents → Add an AI → Custom GPT or HTTP)
Call What it does
GET /api/v1/rules The owner's rules, budgets left and your promises
POST /api/v1/check May I do this? Send what, action (pay, send, share, delete, change, read, other), and optionally amount, site, category, kind, reason_for_owner. Or send items for a whole cart.
POST /api/v1/spend Money was spent outside YeNo: what, amount, site
POST /api/v1/promises promises: plain sentences YeNo will enforce
POST /api/v1/status Has the owner decided yet? Send the request_id from an ask answer

Every answer has answer: yes (go ahead), no (don't; read why and would_be_ok), ask (the owner is deciding on their phone) or trial (written down, not done). A "no" is a normal answer (HTTP 200), not an error; 400 means the request itself was incomplete, 401 means the key is missing or wrong.

curl -X POST https://<yenorules>/api/v1/check \
  -H "Authorization: Bearer <agent key>" -H "Content-Type: application/json" \
  -d '{"what":"Desk lamp","amount":25,"site":"ikea.com","action":"pay","reason_for_owner":"The lamp for the office."}'

Promises YeNo understands

Write them as plain sentences, one each. YeNo reads these patterns:

You write YeNo enforces
Never spends more than $20 a day / a week / a month A running total for your bot; over it is a no
Spends at most $15 per order Any single purchase over it is a no
Only buys from amazon.com and target.com A purchase anywhere else is a no
Never buys from casino.example Those shops are a no
Never buys gift cards or crypto Purchases that mention them are a no
Never sends email / Never deletes anything / Never pays for anything That kind of action is a no
Always asks before sending That kind of action waits for the owner
Read-only Any change is a no

YeNo returns what it understood and lists any sentence it couldn't read, so you can rephrase it.

Promises only get stricter. If you declare a higher limit or more shops later, YeNo keeps the stricter one. Only the owner can remove a promise, with their PIN.

When your bot tries something that breaks a promise, YeNo refuses it, tells your bot why (and, for limits, what amount would keep the promise), tells the owner, and lowers your bot's trust level for a day. Don't retry another way: tell the user.

The "Works with YeNo" badge

You may show the badge if your bot calls declare_promises when it connects and calls check_rules before spending money.

<a href="/"><img src="/works-with-yeno.svg" width="188" height="40" alt="Works with YeNo: this bot keeps its promises"></a>

Put your promises right under the badge, word for word, so people can read exactly what YeNo will hold you to.

Template: Spend Guard (a Grok bot)

A shopping helper that people can trust with a card.

Bot instructions

You help the user shop. You are connected to YeNo. When you connect, call declare_promises with: "Never spends more than $20 a day. Spends at most $15 per order. Only buys from amazon.com and target.com. Never buys gift cards or crypto. Never sends email." At the start of every job, call get_context and follow what it says. Before every purchase, call check_rules with what, amount, site and action "pay". If the answer is no, tell the user why and offer what would be OK. If it asks the owner, wait. After a purchase goes through, call record_spend. If you're in a trial week, say so: nothing you do is real until the owner ends the trial.

Listing text

Spend Guard finds and buys everyday things for you, within limits you can see. Promises (enforced by YeNo): never more than $20 a day or $15 an order; only Amazon and Target; never gift cards or crypto; never sends email. [Works with YeNo badge]

Privacy

YeNo only sees what your bot sends it: the action, the amount, the shop and a few words about it. Promises and rules live with the owner's account; shared rule packs travel in the link's #fragment, which never reaches a server.

Cite this page

, YeNo Rules. “YeNo for bot builders.” Last updated . www.yenorules.com/docs/bots

Share this page

Get YeNo