Where Nymbrink fits

AI agents answer customers, arrange appointments, help employees and work on code. Nymbrink helps you follow the published commitments behind the agents you use, make your own agent’s commitments clear, and keep a record when something needs review.

Why you don’t have to take our word for it

Every use below rests on the Provenance Protocol, an open standard. A company signs its agent’s passport with its own key and publishes it at its own address. Nymbrink checks those signatures, and signs what it records.

  • Anyone can check a signature without asking Nymbrink: in a browser, or with one command.
  • In a passport signed under version 0.2 of the standard or later, changing a single word breaks the signature, so a passport edited after the fact is caught. A version 0.1 signature covers only the agent’s identity.
  • A signature proves who published a passport and that it has not changed. It does not prove the promises in it are true.
Check a signature yourselfThe open protocol on GitHub

Four things you can do

  • Monitor AI suppliers

    Follow a supplier’s signed passport or its public policy pages. See each change line by line, and keep your team’s decision against the version it saw.

    Monitor a supplierSee an example

  • Publish your agent’s commitments

    Sign a passport that says who answers for your agent, what it handles, who else touches the data and what needs a person.

    Publish a passportCreate in your browser

  • Manage internal agents

    Record the agents your company runs for itself: who is responsible, who may see each one, and when one is retired.

    See an exampleAdd an internal agent

  • Disclose findings about your agent

    Tell the customers who watch your agent about an incident, in your own words and signed. Nymbrink’s experimental labels also let you mark a notice as a research finding or an advisory.

    See an exampleYour passports

Agents at work today

Three of these examples link to an account the agent’s provider published about a real deployment. Those companies are not Nymbrink customers, and none of them is involved with or endorses Nymbrink. The customer-support example is made up and names no company.

Customer-support agents

Keep track of the commitments behind your customer-support agent.

Your support agent handles customer conversations. Add the supplier’s relevant public policy pages to Nymbrink, review the wording as first retrieved, and follow later changes. Where the supplier publishes a signed passport, Nymbrink checks its declarations against your requirements. Your team’s review stays tied to the version it saw.
Made-up example: a supplier’s retention statement changes after your team approved the serviceWe keep conversation transcripts for 30 days 90 days.Nymbrink shows the wording before and after, so your team can look again at its decision.

For example: A retailer uses a supplier’s agent to answer customer questions by chat and email, and approved it after reading the supplier’s data and retention terms. This one is made up: it describes no particular company.

Monitor a supplierTry the supplier-change example

Appointment and voice agents

Make the commitments behind your booking agent clear.

If you run a booking agent for your customers, publish who is responsible for it, the services it depends on, the information it handles and the actions that need a person’s approval. They go in a signed passport, and your customers can follow it for changes.If you use another company’s booking platform instead, follow that company’s public policy pages. Running a booking service and relying on the platform underneath it are different responsibilities, and each company answers for its own.

In practice: Retell AI describes TripleTen using a voice agent for admissions outreach and for arranging calls with admissions advisors. Read the provider’s account

Create your agent’s passportMonitor a supplier

Employee-support agents

Keep a clear record of the agents your staff rely on.

Employee-support agents answer workplace questions and handle service requests. For an agent your company runs itself, record the person responsible, what it declares and whether it is current. Choose which colleagues may see it, and record when it is retired.For a service a supplier runs, follow the supplier’s public commitments instead: using it inside your company does not make you its publisher. Nymbrink records declarations and decisions; your own systems control the running agent.

In practice: Moveworks, now part of ServiceNow, describes Broadcom using its AI for IT support and employee onboarding, including account and access requests. Read the provider’s account

Try the internal-agent exampleMonitor a supplier

Coding agents

Follow the published terms behind the coding agents your team uses.

Your engineers work with coding agents. Add the supplier’s privacy, data-use or subprocessor pages to Nymbrink, review later changes in the wording, and keep the record of your team’s decision. Nymbrink follows the published pages you choose; it does not see your code or control what the agent may do.Separately, your own agent can check suppliers through Nymbrink before using them, with a person making every decision.

In practice: Cursor publishes accounts of engineering teams using it, at Stripe, Brex and other companies. Read the provider’s accounts

Monitor a supplierUse Nymbrink with your agent

What Nymbrink does not do

  • It does not judge whether an agent is safe, or decide for you. It records what it observed, and when, and the decision your team made.
  • It reads what suppliers publish. It does not see a contract you negotiated privately, and when a page cannot be retrieved it says so rather than showing the last copy as current.
  • It does not sit in your traffic or stop an agent running. A passport is what the company behind an agent declares, not proof of what the agent does.

Retell AI, Moveworks, ServiceNow, Cursor and the other company names on this page belong to their respective owners, and are used only to refer to their published accounts.