Sign in
AI & MCP

Comparison Coach

Coach two charts on relationship dynamics.

post/ai/comparison-coach

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

questionstring required
language'uk' | 'en' | 'de' | 'ru' | 'pl' | 'es' | 'pt' | 'hi' | 'fr' | 'ko' | 'it' | 'ja' | 'id' | 'tr' | 'nl' | 'ro' | 'cs' | 'vi' | 'ar' | 'el' | 'hu'

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

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

  • dd3764875e7a2See the full diff
    • ○

      added the new optional request property chart1/ayanamsa

      new-optional-request-property

    • ○

      added the new optional request property chart2/ayanamsa

      new-optional-request-property

  • e637d1a9911b43See the full diff
    • ●

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

      request-property-max-set

    • ●

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

      request-property-max-set

    • ●

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

      request-property-min-set

    • ●

      the chart2/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

  • b0533bcc12c0884See the full diff
    • ▲

      the request property chart1/latitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart1/longitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart2/latitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart2/longitude became not nullable

      request-property-became-not-nullable

    • ▲

      the request property chart1/latitude became required

      request-property-became-required

    • ▲

      the request property chart1/longitude became required

      request-property-became-required

    • ▲

      the request property chart2/latitude became required

      request-property-became-required

    • ▲

      the request property chart2/longitude became required

      request-property-became-required

    • ●

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

      request-property-max-set

    • ●

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

      request-property-max-set

    • ●

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

      request-property-max-set

    • ●

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

      request-property-max-set

    • ●

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

      request-property-min-set

    • ●

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

      request-property-min-set

    • ●

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

      request-property-min-set

    • ●

      the chart2/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 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

    • ○

      the longitude request property default value 0 was removed

      request-property-default-value-removed