What is getting in the way
Sending an unlisted URL is not an access policy. It is hard to revoke, easy to forward, and gives neither you nor the client a clear boundary around identity and authority.
Private client delivery
Client-facing AI agent with real private access
A client-facing AI agent should verify who is allowed in, keep access revocable, and leave the Agent's instructions, tools, and shared knowledge under your control.
What changes
Publish the Agent privately, grant exact people or domains through OAuth, or issue a scoped API key when server-to-server access is the better fit.
Private client delivery
How Prostir gets you there
List the allowed clients
Decide whether access belongs to exact verified email addresses, exact normalized domains, or a named API integration.
Choose the access mode
Use OAuth for people or create a scoped, expiring, revocable API key for an explicit machine-to-machine need.
Publish and review
Confirm the policy before publication, then monitor and revoke grants or keys without rewriting the Agent.
Early access
What you can verify
- New Agents are private by default and begin with OAuth protection rather than anonymous access.
- OAuth policy uses exact verified emails or normalized exact domains and rejects suffix-style matching.
- API keys are Agent-scoped, named, expiring, revocable, rotatable, shown once, and stored hashed.
A good fit if
- You deliver an Agent to named clients, companies, or approved integrations.
- You need the customer to use the Agent without editing its core configuration.
Not the right fit if
- You want an untracked public link to count as private access.
- You need several coworkers to edit shared Tasks, Files, Data, and Knowledge; that is a Team use case.
Questions before you decide
Can I allow a whole client company?
Yes, with a normalized exact-domain OAuth grant when that policy is appropriate. Similar-looking domains, suffixes, and unverified email claims do not qualify.
Can a client change the Agent?
No. A standalone Agent remains author-controlled. Clients can use their explicitly owned personal context, but they cannot mutate the shared instructions, tools, Skills, or Agent Knowledge.
Explore related options
Early access
Design access before you send the link
Tell us who the clients are, how they should sign in, and what should remain owner-only. We will map the correct private Agent boundary.