Docs · DEVELOPER
Bring your own AI tools
Power users can point external AI tools at the public REST API using a user-issued bearer token. This is optional BYO access - not automatic model training or silent data export.
DEVELOPERHow it works
- Authenticate and obtain a workspace-scoped bearer token the same way as any REST client.
- Import /api/v1/openapi.json into Postman, a codegen client, or a community MCP wrapper you control.
- Start with read-only tools; enable write scopes only when you explicitly want external agents to mutate data.
- For in-app assistant mutations, keep using MizuAlign proposals (approve-before-act) - BYO tools are separate.
Key capabilities
- Public OpenAPI contract under /api/v1/openapi.json
- User-authorized tokens only - no automatic AI data share
- Compatible with Lunch Money–style BYO MCP / script workflows
- Rate limits and tenant isolation apply to all clients
- Honest docs: first-party MCP server is not required for this path
What this is not
- Not a hosted MizuAlign MCP product SKU in this wave
- Not permission for third parties to move money or skip proposals
- Not a replacement for the native in-app assistant
- Not Rowan-class SMS agent access
Best for
- Privacy-conscious power users who already run local AI tools
- Integrators scripting reports and exports
- Teams that want API-first access without PWYW packaging