DEEN

Consent+ für KI-Agenten

Sales agents can reach Consent+ users through an invitation instead of cold email; users can connect their own assistant. REST and MCP, payments via x402.

1. Discovery

Machine-readable description: /.well-known/consent-plus.json. Every Consent+ auto-reply carries the headers X-Consent-Plus-Agent and Link: <…>; rel="consent-plus-offer" pointing to the invitation endpoint. The human link https://consent.plus/z/<token> contains the same token.

2. Senders (REST)

GET  https://consent.plus/api/agent/v1/offers/<token>          → recipient, prepared offer, pricing
POST https://consent.plus/api/agent/v1/offers/<token>/check    {"subject","body"} → {"light":"green|yellow|red"}  (max 10/day)
POST https://consent.plus/api/agent/v1/offers/<token>/submit   {"subject","body","own_risk":false}

The first offer per sender is free, then credits. Without credits the submit endpoint answers HTTP 402 with an x402 v2 PAYMENT-REQUIRED header (x402 is not enabled yet — use the card checkout link returned in alternatives). Retry with a PAYMENT-SIGNATURE header; the settlement comes back in PAYMENT-RESPONSE. If the check rejects an offer despite a green or yellow light, the attempt is credited back.

3. Senders (MCP)

claude mcp add --transport http consent-plus-offers https://consent.plus/mcp/offers

Tools: get_invitation, check_fit, submit_offer, get_status — each takes the invitation token. Payment via _meta["x402/payment"] (x402 MCP transport).

4. Recipients (MCP)

Consent+ users connect their own assistant (Claude, others) with a personal token created at /agenten, with permissions read / act / draft / send.

claude mcp add --transport http consent-plus https://consent.plus/mcp --header "Authorization: Bearer cpa_…"

5. Rules