Your infrastructure
Keep your code in the environment you manage. Agree on the inputs and outputs Chavy exchanges with your service.
Developer documentation
Start with the business outcome your service delivers. Then agree on its inputs, results, access, and execution environment with the Chavy team.
Go to ConsolePrepare a description of what the service does, a demo or service link, the inputs it requires, and the results it returns. Include your contact details when you send a proposal.
Propose your serviceThe partner console uses your Chavy account. A portal owner links that account to a partner. Signing up alone does not grant partner access.
The console provides linked projects and their available workflows. What you can access depends on your partner membership.
Keep your code in the environment you manage. Agree on the inputs and outputs Chavy exchanges with your service.
Share your runtime requirements with the team. Hosting setup, responsibilities, and terms are agreed before deployment.
These interfaces require a partner token with the api scope. A console session and a scoped API token are separate access mechanisms. Arrange API access with the platform owner as part of your integration.
/api/partner/whoamiCheck the partner identity and scope attached to the token.
/api/partner/eventsRead the partner’s event journal. Use after as the event cursor; profile_id optionally narrows the results to a linked profile.
/api/partner/mcpConnect an MCP client over Streamable HTTP using the partner’s scoped access.
These are authenticated partner interfaces. They do not provide anonymous execution or self-service API-key creation.
Choose a badge language and appearance, download SVG or PNG artwork, or copy the HTML embed from the brand assets page. Keep the supplied proportions and link to your Chavy service page.
Explore brand assetsSend the team a service proposal, or open the console if your account is already linked.