Sign in
MCP Advanced

MCP Agent Debate

2 personas debate a topic, multi-round transcript.

post/mcp/agent-debate

Headers

X-Provider'openai' | 'anthropic' | 'google' | 'groq' | 'mistral' | 'openrouter' | 'deepseek' | 'together'

Bring your own model key: the LLM provider that should run this completion. Send together with X-Provider-Key or the request is refused: a key with no provider bills us for tokens you meant to pay for, and a provider with no key would look like it worked. The endpoint is fixed per provider on our side and is never taken from the request. There is no fallback to our own chain: if your key fails you get the provider's status and message.

X-Provider-Keystring

Your own credential for X-Provider. Never logged, stored or cached: it travels in a header because the request body is hashed into two cache keys, and a BYOK turn bypasses both caches in each direction. A provider error that quotes the key back is redacted before it reaches our logs or your response. Such a turn costs 5 credits instead of the endpoint price, and only when a completion actually ran on your key.

X-Provider-Modelstring

Optional model id, overriding the default for that provider. Defaults: openai → gpt-4o-mini, anthropic → claude-sonnet-4-5, google → gemini-2.5-flash, groq → llama-3.3-70b-versatile, mistral → mistral-large-latest, openrouter → meta-llama/llama-3.3-70b-instruct, deepseek → deepseek-chat, together → meta-llama/Llama-3.3-70B-Instruct-Turbo.

Request body

topicstring required
agentAstring required
agentBstring required
roundsinteger
language'uk' | 'en' | 'ru' | 'es' | 'pl' | 'de' | 'fr' | 'it' | 'pt'

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

Changed in 3 of the 13 revisions of this API.466

  • dd3764875e7a1See the full diff
    • ○

      added the new optional request property chart/ayanamsa

      new-optional-request-property

  • e637d1a9911b23See the full diff
    • ●

      the chart/timezoneOffset request property's max was set to 14.00

      request-property-max-set

    • ●

      the chart/timezoneOffset request property's min was set to -14.00

      request-property-min-set

    • ○

      added the new optional header request parameter X-Provider

      new-optional-request-parameter

    • ○

      added the new optional header request parameter X-Provider-Key

      new-optional-request-parameter

    • ○

      added the new optional header request parameter X-Provider-Model

      new-optional-request-parameter

  • b0533bcc12c0442See the full diff
    • ▲

      the request property chart/latitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart/longitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart/latitude became required

      request-property-became-required

    • ▲

      the request property chart/longitude became required

      request-property-became-required

    • ●

      the chart/latitude request property's max was set to 90.00

      request-property-max-set

    • ●

      the chart/longitude request property's max was set to 180.00

      request-property-max-set

    • ●

      the chart/latitude request property's min was set to -90.00

      request-property-min-set

    • ●

      the chart/longitude request property's min was set to -180.00

      request-property-min-set

    • ○

      the latitude request property default value 0 was removed

      request-property-default-value-removed

    • ○

      the longitude request property default value 0 was removed

      request-property-default-value-removed