Products don't want providers, they want capabilities.
APINIREYA is the single gateway through which Nireya products connect to outside services. A capability ledger, a permission ledger, a secret vault and evidenced execution: secrets stay in the vault, and every action closes with its evidence. Nirmind, NirArmy or Claude simply says “send an email”; the gateway decides which provider, which permission and which approval it takes.
9
Capability contracts
7
Providers (Gmail, Calendar, WhatsApp…)
129
Tests · 0 failed
MCP
Capabilities as tools
Live preview
Panel on the web, app in your pocket.
Click through the menus in the panel on the left, then tap “Start preview” on the phone to the right — just as if APINIREYA were really running.
Capabilities
Capabilities
9
contracts
Providers
7
seeded
Pending approvals
1
IRREVERSIBLE
Tests
129
0 failed
Executions
liveBreakdown
Capabilities
Capabilities
9
contracts
Providers
7
seeded
Pending approvals
1
IRREVERSIBLE
Tests
129
0 failed
Executions
liveBreakdown
Capability Ledger
Ask for the job, not the provider.
Products ask for capabilities such as “Send email”, “Read calendar” or “Check availability”. Every capability is tagged READ, REVERSIBLE or IRREVERSIBLE; anything that cannot be undone lands in the approval queue.
- 9 capability contracts
- READ · REVERSIBLE · IRREVERSIBLE
- Industry adapters
Connections
Capabilities
9
contracts
Providers
7
seeded
Pending approvals
1
IRREVERSIBLE
Tests
129
0 failed
Executions
liveBreakdown
Vault & Permission Ledger
Secrets stay in the vault.
API keys and OAuth tokens never leave the vault; which product may use which capability is written in the permission ledger. The default answer: deny.
- Secret vault
- Permission ledger
- Deny by default
Approvals
Capabilities
9
contracts
Providers
7
seeded
Pending approvals
1
IRREVERSIBLE
Tests
129
0 failed
Executions
liveBreakdown
Evidenced Execution
No evidence means it never happened.
The execution engine meters every call, passes it through the approval queue and closes it with evidence. Thanks to the MCP face, clients like Claude see capabilities as tools.
- Execution engine
- Meter and approval queue
- MCP server face
Capability contracts
lib/capabilities.ts
Providers
Seeded connections
Immutable rules
The gateway's constitution
Everything that comes with APINIREYA.
Vault
Secrets never leave the process.
Capability ledger
9 contracts, with effect classes.
Permission ledger
Deny by default.
Execution engine
Gmail OAuth and industry adapters.
Approval queue
Approval can only get stricter.
Meter
Every call is measured.
MCP face
Capabilities as tools.
Evidence
Every action closes with evidence.
Powerful on its own. Limitless with the ecosystem.
With a single Nirpax identity, APINIREYA talks seamlessly to every other product in the Nireya ecosystem.