Contact
Tell us which agent to start with.
Whether you own non-human identity posture, operate the identity control plane, or ship agents on deadline, the fastest way to see Mandavo is to name one agent and one system it touches. Write to us, and a named human on the team reads and replies.
Before you write
What to expect when you reach out.
Who reads my message?
A named human on the Mandavo team reads and answers every message. There is no autoresponder standing in for a person.
What is useful to include?
Name one agent, the system or API it needs to reach, and how it authenticates today — a shared service account, a static key, or a borrowed human login. That is enough for us to talk about issuing it a distinct, short-lived identity scoped to a named sponsor.
I am shipping agents now — can I try the self-serve credential flow?
Tell us what you are building and where you are hardcoding keys today. We will walk you through obtaining a scoped, short-lived credential through a self-serve request rather than committing a static secret to code or config.
Can we discuss cross-counterparty verification?
Yes. We are candid about the boundary: control and enforcement inside your own tenant is available today, and the verification API lets a counterparty check a credential's authority, scope and revocation status before transacting. We will describe what is in place and what is still ahead.
Is there another way to see the product?
The product and pricing pages describe what Mandavo issues, enforces and verifies, and how it is packaged. Write to us and we will answer the questions those pages do not.
Prefer to read first?
See how Mandavo issues each agent a distinct identity, enforces authority at the moment of execution, and lets any counterparty verify it — before you write.