Consent

Approval step of the MCP OAuth flow. Three roles share it:

  • owner exposing a set of their memory views → mints a provision_view_binding;
  • owner exposing their own agent → mints a provision_agent_binding (the owner gate lives in provision_*, which is @owner_only);
  • buyer connecting a purchased listing (kind='listing') → re-issues the existing cross-tenant listing credential, gated by an active grant in reissue_memory_listing_credential (never charges, never provisions new access). Either way the token is wrapped in a one-time code.
post/v1/oauth/consent

Request

  • Base URL: https://api.app.membase.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.app.membase.ai/v1/oauth/consent
  • Auth: none declared

Request body

client_idstring required
redirect_uristring required
code_challengestring required
resourcestring
statestring
approveboolean
kindstring
subject_idstring
subject_idsstring[]
profile_accessboolean

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.