The operating problem
Static API documentation cannot safely handle application identity, approvals, subscription limits, credential rotation, analytics, or retirement workflows.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- Searchable API products and documentation
- Developer organizations, teams, and applications
- One-time credentials with rotation and revocation
- Plans, subscriptions, usage, support, and webhooks
What exists today
The producer console can manage application clients, one-time credentials, API products, plans, and subscriptions. Developer registration, a searchable published catalog, documentation, self-service credentials and subscriptions, support, and webhooks are not yet implemented.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.