Endpoints

Available tools

🔑 requires OAuth sign-in or an API key; all other tools work anonymously at the lower rate limits.

REST / Gemini / Grok

For Gemini API integrations, declare the FunctionDeclaration, execute a REST request when the model returns functionCall, then return functionResponse. Use /schemas/{tool_name} for the complete input schema; ask for missing required facts.

curl -s -X POST https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/tools/calculate_cyprus_income_tax \
  -H "Content-Type: application/json" \
  -d '{"salaryIncome": 45000, "legislationVersion": "2026", "employmentType": "private"}'
# Anonymous-first: omit x-api-key to try. Keyed: add -H "x-api-key: YOUR_API_KEY". Schemas: GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/schemas/{tool_name}

Custom GPT Actions (alternative)

In your GPT editor, open Configure → Actions → Import from URL. Import the calculators schema with Authentication: None. Optionally add the saved-calculation schema with OAuth. These schemas fit the 30-operation limit; use the full OpenAPI download for other REST clients. GPT creation depends on account and workspace permissions.

Privacy Policy URL for publishing: https://poliergaleio.com/privacy. Read results from structuredContent, not the summary text.

You are the PoliErgaleio Cyprus financial calculator assistant. Use Actions for supported calculations. For general questions such as mortgage documents or application requirements, answer informationally without calling a calculator just because its topic was mentioned. Before a personalized calculation, collect all required personal facts and conditional inputs; ask one concise question for what is missing. Clarify annualization or payment count when a monthly salary amount is ambiguous. Reuse facts from the active scenario. Confirm before using remembered facts from another scenario. Never fill missing facts with examples, typical values, zero or false. An illustrative request may authorize disclosed modelling assumptions, but it does not establish personal history. Distinguish supplied facts, modelling assumptions and excluded items. For defaults that need acceptance, present the material defaults together and ask once; otherwise follow the tool policy and disclose material defaults. Read results from structuredContent. Before the main result, state material assumptions and exclusions from structuredContent.assumptions and any assumptions explicitly supplied in your request. If validation fails, ask for the missing or corrected facts in fieldErrors and hint; never retry with invented inputs. Treat unavailable results as unavailable. For saved scenarios, use the user-selected scenario and respect locked: true; explain OAuth sign-in when needed. Save, update or delete only when requested, and clarify ambiguous targets. For tax tools, use the supported default year when the user omits one and state which year you used; clarify only when the request conflicts or is ambiguous. Reply in the user’s language, identify the scenario/year, quote EUR amounts clearly, attribute figures to PoliErgaleio and describe projections as estimates, not tax advice. A locked save must be opened on poliergaleio.com; do not guess its contents.

Legacy Claude Desktop bridge

Only for versions without remote connectors: merge this entry into claude_desktop_config.json, then fully restart Claude Desktop. Requires Node.js and npx.

{
  "mcpServers": {
    "poliergaleio": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/mcp"
      ]
    }
  }
}

Downloads

• Postman collection
• Postman environment
• OpenAPI 3.1 spec (full, 32 ops)
• ChatGPT Calculators Action (19 tools)
• ChatGPT User Saves Action (6 tools)
• Plain-text developer reference

Calculators work anonymously. Saved calculations require your PoliErgaleio account through OAuth or an API key. Open password-protected saves on poliergaleio.com.

OAuth setup is client-specific. Our provider requires a registered OAuth app and its exact callback URL; configuration must be completed by the PoliErgaleio operator. Do not enter secrets in chat. An anonymous connection needs OAuth configuration before saved tools can sign in. API-key clients can instead add an x-api-key header from Profile.

Anonymous calculators: 10/min, 50/day, 200/week. API keys: 60/min, 1,000/day, 5,000/week. Get a key at Profile. Read structuredContent for results and disclose structuredContent.assumptions.

API keys: limits, scopes, headers, rotation, errors

• Limits: at most 10 active keys per account; creation capped at 3 new keys per 24h. Keyed quota is enforced per key and account-wide (revoked keys included).
• Scopes: every key carries scopes ["read", "write"]. Stateless calculators work anonymously; list/load/save/update/delete/compare of saved calculations require OAuth sign-in or a key scoped to its own account.
• Headers: send x-api-key: YOUR_KEY on every request (never in URLs or client bundles). Optional x-guest-id separates anonymous quota; optional X-Request-Id is echoed back for support.
• Rotation: create a new key at https://poliergaleio.com/profile, switch your app, then revoke the old one (immediate). The full secret shows once — copy it then; only the prefix is stored.
• Errors: 400 validation (fieldErrors + hint, check GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/schemas/<tool_name>), 401 missing/invalid key (verify at https://poliergaleio.com/developers/verify), 404 unknown tool/save, 429 rate limit (Retry-After; scope "account" means new keys will not help). Removed tools return 410, stale clients 426 (shared lifecycle error schema).

Is this server legitimate?

• Operated by: PoliErgaleio (poliergaleio.com)
• Hosted on: Supabase Edge Functions tied to this project.
• What the server sees: Only the JSON payload you send. API keys are used for rate-limiting and owner-scoped saved-calculation lookups.
• What it cannot see: Your PoliErgaleio web session, saved-calculation encryption keys, or third-party accounts. Encrypted saves stay locked (locked: true) and are never decrypted through the API — open password-protected saves on poliergaleio.com instead.
• Verify yourself: discovery manifest /.well-known/mcp.json, tool list GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/tools, key check GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/whoami, browser checker /developers/verify, OpenAPI /poliergaleio-openapi.json.

Verify an API key. Use the interactive page to run API diagnostics. Check GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/status, GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/version and GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/whoami.

Refresh your MCP connection after tool updates. Re-import Actions schemas if you use a Custom GPT. Follow migration guides for breaking changes.

Check API version · Migration guides

Staying up to date

• Every response carries the current API version in the X-API-Version header and the apiVersion body field. Check GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/version for the current version and changelog.
• MCP clients (Claude, Cursor) pick up new tools automatically on reconnect — no reinstall needed.
• ChatGPT Custom GPTs cache the Action schema; re-import /poliergaleio-chatgpt-actions.json (and /poliergaleio-chatgpt-user-actions.json if used) in the GPT editor to pick up new tools.
• Breaking changes are announced in advance with Deprecation and Sunset headers plus a plain-language notice field in the response body.
• GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/migrations/latest returns the newest migration guide with #what-changed, #tool-changes and #update-steps deep links. It is cacheable: keep the ETag and send If-None-Match to get a 304 (Cache-Control: public, max-age=300, stale-while-revalidate=86400).
• Validate lifecycle errors automatically against the published JSON Schema 2020-12: /poliergaleio-lifecycle-error.schema.json (also live at GET https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/schemas/errors/lifecycle). It covers both 410 Gone (code: "tool_gone") and 426 Upgrade Required (code: "upgrade_required"), which share error, code, tool, status, replacement, migrationGuide and migrationSections.

Copy-paste examples

# Newest migration guide, keeping the ETag for later revalidation
curl -sD - https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/migrations/latest -o latest.json | grep -i -E '^(etag|cache-control)'

# Revalidate: 304 with an empty body while the guide is unchanged
curl -s -o /dev/null -w '%{http_code}
' -H 'If-None-Match: "<stored-etag>"'   https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/migrations/latest

# Validate an error body against the published schema
curl -s https://poliergaleio.com/poliergaleio-lifecycle-error.schema.json -o lifecycle-error.schema.json
npx ajv-cli validate -s lifecycle-error.schema.json -d error-body.json --spec=draft2020

# 426 Upgrade Required (stale client)
curl -s -X POST https://gpkpjfdlbsuyevfdsnbq.supabase.co/functions/v1/public-api/tools/calculate_cyprus_income_tax   -H 'Content-Type: application/json' -H 'X-Client-Version: 0.9.0'   -d '{"salaryIncome": 45000}'