- Summary: /llms.txt
- Status: early access. Self-serve sign-up for agents is being built.
What Reynforce is
A register of the facts your company stands behind, each with a named owner and a date it was last checked; a mandate saying what you may promise and spend; and a record of every promise made in your company's name. Before you quote a figure, a discount or a date, you ask. The answer is allowed, needs approval or not allowed, with the reason and the fact it rested on, and every answer is recorded. Today it records rather than blocks: the answer says so.
How you sign yourself up
- Ask for access. Send a POST to
https://app.reynforce.com/request-access, as JSON or as a form, with the fields below. - A person reads it. Nothing is emailed automatically yet: somebody at Reynforce reads every request and gets in touch with the person you named, and the answer says
"emailed": falseso you know. At most 50 requests are taken a day, across everybody. - Your owner signs in. There is no link that grants ownership to whoever holds it: signing in is what makes them the owner, and they issue your key.
company | your company, up to 120 characters |
|---|---|
owner_email | the email address of the person responsible for you, up to 254 characters |
agent | your own name, if you want to give one, up to 64 characters |
Or a person at your company signs it up themselves at https://app.reynforce.com/signup. 14-day free trial, and nothing is charged during it.
Where you connect
MCP https://app.reynforce.com/t/<your workspace>/mcp
HTTP https://app.reynforce.com/t/<your workspace>/v1/observe
- The MCP door —
https://app.reynforce.com/t/<your workspace>/mcp, over Streamable HTTP, withAuthorization: Bearer <your key>. Use this if you can speak MCP. - The HTTP door —
https://app.reynforce.com/t/<your workspace>/v1/observe, with the same key, for a tool that cannot speak MCP; it also answers/v1/unchecked,/v1/health. /openapi.json describes it.
Your key is shown once, to the person who issues it on your workspace's screen. /agent-quickstart.md has the three steps, and /examples.md three worked checks.
What you can check, and the tools you hold
Your key holds these, and nothing else:
search_claims— read the register: each fact comes back with its owner, its last check and whether you may use it.check_action— ask whether an action is allowed before you take it, and what to say instead when a fact it cites is not usable. The check is recorded.report_said— after a message went out or a call ended, hand over what was said, so the promises in it are recorded.approval_status— ask how a request for approval went. It is never a yes on its own.
Setting you up is a person's job. These two are for a signed-in person at your company, from ChatGPT or Claude for example, and your key never holds them — so you cannot change the rules you are held to:
setup_guide— what is left to set up — rules approved, facts usable, an approver named, an agent connected, its first check — and the tool that does each.connect_platform— the steps for the platform you run on, in its own field names, and where your key is made. Never the key itself.
What it costs
- Do it yourself: £99 a month each for your first 10 agents and £79 for each one after, up to 49, so adding an agent never lowers the bill. Pay yearly and get two months free: £990 and £790 per agent a year. Free for 14 days.
- The 7-Day Agent Approval: done for you, sold in a call — Complete £7,000 · Standard £4,500 · Starter £2,500.
- The price is the same whoever pays, including you paying for yourself, and there is no charge per check. These are early prices that we are testing in conversations, and they may change.
How a person approves
- Facts you draft stay proposed. A person at your company signs in to the workspace and accepts them. Until then, a check against one answers not yet confirmed by a person, never allowed.
- You cannot accept your own facts or approve your own mandate, and paying does not change that. Paying buys the service, not the authority. That is what makes the record worth showing.
- When a check needs approval, the person who can give it is emailed a link, and they answer on the workspace's own approvals page. You ask
approval_statushow it went. - When a fact is not usable, tell the buyer you are checking. Do not answer around it — that is the one thing this exists to prevent.