OpenAPI
API reference
Endpoints, schemas, a playground. Developers read it. A docs job.
[api documentation software]
API documentation software is a reference. Oppulence is a write gate.
API docs software hosts OpenAPI, a try-it playground, and a changelog. Oppulence separates recommendation, policy, approval, execution, and outcome so a write to mail or CRM stays auditable.
Free first reportApproval before anything leavesNo invented case studies
[definition]
What “API documentation software” actually means
API documentation software publishes a reference next to your product docs. Mintlify, Redoc, and Ferndesk's API docs surface do that. Oppulence does not host your OpenAPI. This leftover slug is the governed-execution page: verification, suppression, permission, and approval before a connector writes.
Three jobs that are not the same.
Governed actions
Connector write
gmail_send, a Slack message, a HubSpot note. Customer-facing. Gated.
Contracts
MCP contract
A tool you added. Review inputs and failure modes before an agent calls it. The validator route is a frame, not a hosted spec site.
[for]
This page is for you if
- You already write promises in mail, Slack, and calls, and they disappear.
- You want a register with sources, not another place to type notes.
- Customer-facing sends should wait for a person.
[not for]
This is the wrong page if
- You need a public help center, article CMS, or ticketing inbox. That is a different product.
- You want a bot that sends as you without approval.
- You want a wall of logos and invented time-saved numbers. We will not publish those.
Questions this URL actually answers
The leftover slug is a search path. The answers stay honest about the product.
No. docs.oppulence.io is the API reference for Oppulence itself. We are not an OpenAPI publisher for your product.
