Version
DESTRUCTIVE

accept_partner_terms

Record that the token's creator accepts the Partner Program Terms as they stand, which every payout rail requires. Idempotent.

Record the acceptance the dashboard's payout dialog and the bot record, with the terms version as it stands today. Accepting again after the terms change is the same call, so an agent can run it whenever the partner object shows terms_accepted_at as null or an older terms_version. Only an approved partner has terms to accept: an application still under review is refused with the dashboard's sentence.

Synchronous. Answers the partner object as get_partner_program describes it, with terms_accepted_at and terms_version set. Takes no input. Emits no event.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

DestructiveIdempotent

A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.

Arguments

This tool takes no arguments.

What it returns

{  "data": {    "id": "4b7e2d19-5c3a-4f80-9e6b-1d2c3b4a5f60",    "status": "active",    "terms_accepted_at": "2026-10-21T08:00:00+00:00",    "terms_version": "2026-10-10"  }}

How it fails

VALIDATION_FAILED

the application is still under review or was declined.

RESOURCE_NOT_FOUND

the creator never applied to the programme.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks account:write.

How is this guide?

Last updated on