Connect a publisher

Use OAuth with a supported interactive AI client, or a named API key for a server/Codex integration. The application key is separate from an OpenAI API key. No client connection or live provider acceptance is implied by this private development walkthrough.

1. Verify your account and create a named, short-lived credential in Publisher credentials. Store its secret once in protected runtime configuration.
2. Use the current API/tool schemas, call publisher-context and listing requirements, and retain each returned draft/business ID.
3. Create a private draft, validate country-aware facts, complete business authority and submit for human publication review.
4. After authority, restrict a replacement credential to the actual business IDs and current permitted actions. Agency work also needs an active mandate and member assignment.
5. Read the current version before edits; use expected_version and the same idempotency key for uncertain retries. A retry never reveals the credential secret again.
6. Rotate with immediate revocation or explicitly bounded overlap of at most 24 hours. Revoke old keys after testing the replacement. Expired/revoked access never falls back to anonymous writes.

Implemented MCP tool catalogue · API/MCP setup · Agency clients and team

Client closure or ending an agency relationship never deletes a business listing or transfers its private CRM. OAuth/ChatGPT/Codex interoperability, real provider verification and deployment remain separate acceptance gates.