oathe / engineering

Oathe vs A2A: what A2A covers and what you get from Oathe

A2A lets agents send each other work. Oathe keeps an accountability trail of what each agent said it did and what it actually did, inside your team and between companies.

A2A is an open agent-to-agent protocol. It’s a standard set of messages one AI agent uses to find another, send it work and get a result. With A2A alone, you take each agent’s word for what it did.

Oathe is an agent network built on A2A, MCP and ANP (Agent Network Protocol). With Oathe, everyone’s AI assistants and agents work together reliably. Work moves between your agents, your devices, your coworkers, the cloud and other companies. You hand work off safely, Oathe makes sure it’s completed, and a record of the work stays with the company it belongs to.

With A2A alone, the other agent reports completed itself. With an Oathe handoff, your coworker accepts or rejects and their part is checked. Between two companies, Oathe is a neutral third party.

What does the A2A protocol do?

The project says: “The A2A protocol is an open standard for communication between AI agents.” (What is A2A?, read 15 November 2026.)

The specification page lists 1.0.0 as the latest released version. The repository’s latest tag is v1.0.1 (28 May 2026). The Linux Foundation governs the project. (Specification, releases and home page, read 15 November 2026.)

  • Agent Card. A JSON file that says what an agent can do and how to sign in to it. Other agents find it at /.well-known/agent-card.json.
  • Messages and tasks. One agent calls SendMessage (message/send before 1.0). The other answers straight away, or opens a task and reports on it until it reaches a final state such as completed, failed, canceled or rejected. The sender reads the task with GetTask (tasks/get before 1.0). A task can also pause to ask for input (TASK_STATE_INPUT_REQUIRED). (What’s new in v1, read 15 November 2026.)

What does A2A leave to you?

Quotes are from the project’s enterprise page and discovery page, read 15 November 2026.

  • Whether completed is correct. The spec defines completed as “a task has finished successfully.” The agent that did the work reports it.
  • Identity. The Agent Card lists the sign-in schemes an agent accepts. Getting and trusting credentials is outside the protocol. “A2A protocol payloads, such as JSON-RPC messages, don’t carry user or client identity information directly”.
  • Permission. “Authorization logic is specific to the agent’s implementation, the data it handles, and applicable enterprise policies.”
  • Finding a particular agent. “The current A2A specification does not prescribe a standard API for curated registries.” You set up how to reach one named coworker’s assistant.

What do I get from Oathe that A2A alone doesn’t give me?

Oathe keeps an accountability trail for A2A. Before a coworker’s part comes back to you, a fresh checker that didn’t do the work compares what their agent did with what it said and what was asked.

You hand work to a coworker in plain words. Tell your agent “send this to [email protected]”. Your coworker gets Accept or Reject, and you keep your task. Their agent receives the work, the context it needs from you, and any files and folders it needs and doesn’t already have. Inside a company, that handoff is a combination of MCP and A2A.

Your own work moves between your agents and your devices, and with Oathe Cloud it keeps going while your devices are offline.

Everyone already has an agent. Oathe is a way for them to work together. An agent network for your team: agent-to-agent handoff between your AI assistant and your coworkers’, checked when it comes back. What is an agent network? explains the name.

How does Oathe carry work between companies?

Over A2A. Oathe speaks the latest A2A version, with one Agent Card per person. Oathe is a neutral third party between the two companies, and it checks what agents say against what they did.

If both companies run on Oathe, work is checked on both ends before any exchange of information is allowed.

If the other company isn’t on Oathe, only your agent’s work is held accountable. There’s no way to verify their work. Communication is kept secure.

Trust between companies goes through WorkOS, for sign-in and organization membership.

Your record of what your agents did stays with you, for your own records and audits. Theirs stays with them.

When do I not need Oathe?

A2A alone is enough when:

  • You’re building agents as services that call each other, and your own code decides what counts as finished.
  • You want your assistant to message an existing A2A agent. The A2A project ships a command-line tool for that, so your coding assistant “can discover, message, and delegate to any A2A agent.” (a2a-protocol.org, read 15 November 2026.)

Use Oathe when you need that trail, whether an agent belongs to a coworker or to another company.

Oathe vs A2A: comparison table

You want toA2A aloneOathe, built on A2A
Send work from one agent to anotherYes.Same. Inside a company, handoff is a combination of MCP and A2A.
Know that completed is correctThe agent that did the work reports it.Oathe checks what agents say against what they did.
Let a coworker agree before their agent takes itThe receiving agent can pause for input or return rejected. Asking the right person is left to you.Your coworker gets Accept or Reject.
Work with another company on OatheYes, on each agent’s own report.Work is checked on both ends before information is exchanged.
Work with a company that isn’t on OatheYes, on each agent’s own report.Only your agent’s work is held accountable. There’s no way to verify theirs.
Set up trust between companiesOutside the protocol.Through WorkOS.
Keep a record of the workEach agent keeps its own.It stays with the company it belongs to.

Where do I get Oathe?

Oathe is open source under Apache-2.0, at github.com/oathe-ai/oathe. It’s free and installs today with no account.

npm install -g @oathe/oathe
oathe init

Running it yourself takes Node 22.13 or newer and Postgres. Oathe Cloud is hosted, needs neither, and is free in beta.

Two coworkers can hand off on the open-source package alone if your team hosts it. That takes deep thought about security, and moving it to object storage on the internet. Oathe Cloud handles all of this. Only your organization can read what it uploads. Join the waitlist. Setup is in the docs.

Questions

What is the A2A protocol? An open standard for AI agents to find each other, send work and track it.

Is A2A the same as MCP? No. MCP connects one agent to its tools and data. A2A connects agents. See Oathe vs MCP.

Does a handoff to a coworker use MCP or A2A? Both. Inside a company, an Oathe handoff is a combination of MCP and A2A. See connect your AI assistant to a coworker’s.