Identity integrations
Connect Entra ID, Google Workspace, Okta and directories.
2AYE Marketplace
Connect governance to every reachable system.
Governed integrations for identity, cloud, infrastructure, financial, communications, and AI-agent ecosystems.
What this includes
- A browsable integration catalog
- MCP gateway and an allowlisted HTTPS connector
Purpose-built capabilities
Cloud and infrastructure
Govern access to protected resources and workloads.
MCP and agents
Front tools and frameworks with explicit, per-action authority.
Connector evidence
Version permissions, decisions and operational health.
Where 2AYE Marketplace is used
Situations this is built for.
An agent platform team
Tools reach production systems through a gateway, and the gateway's only question today is whether the caller has a key.
→Each tool call carries an evaluated, single-use grant, and the tool key is bound into what was authorized.
A vendor integration owner
Connecting a system means handing over a long-lived credential that nobody can scope or watch.
→A connector runs under a signed contract with its own bounds, and every call it makes is a decision on the record.
Procurement and risk
A connector catalog is a list of logos, and the question "what can this one actually do here" has no answer.
→Each entry states its status and its provenance, and none of them claims to be available without an adapter behind it.
Control path
From verified context to reviewable evidence.
A connector is a bounded authority, not a key exchange. What it may do is written into the contract it runs under, and what it did is on the same evidence chain as every other action.
- 01Select
- 02Scope
- 03Authorize
- 04Connect
- 05Monitor
Enterprise adoption
Move from evaluation to controlled production.
Pick one system
Choose a connected system where an ungoverned action would be material.
Write the bounds
Say what may be done there, by whom, up to what, and for how long.
Front it
Route the calls through the gateway and keep the receipts.