Xynthera AI

Prepaid HTTP APIs

Integrate invoice, OpenAPI contract and event checks.

New purchases use a one-time budget from €10 to €10,000 including applicable taxes, without a subscription or automatic recharge. Your saved private budget code is the Bearer credential. Use the three available operations from your server and save each returned report yourself.

Start with an input example and exact pricesDownload prepaid integration kit

Prepaid OpenAPI: three operations · Python, JavaScript, curl, Postman and n8n HTTP guide · Choose or recover your budget.

Connect a local AI client

Use the Node.js 20+ local MCP adapter with your privately configured budget code. Its default session ceiling is zero: paid checks are blocked until you explicitly set a positive consumption limit. The adapter connects to the existing cloud HTTP APIs; it is not a remote OAuth or ChatGPT connector. Three-step setup and private Claude Desktop configuration.

Existing assurance and subscription documentation

The documentation below describes previously accepted assurance/subscription interfaces. Its x-api-key credentials, monthly quotas and SDKs do not authenticate the prepaid Bearer budget. No MCP payment or automatic recharge is provided.

Free tools

Receipt Check · Contract Check · Event Check · Workbench API.

Xynthera AI Registration runs the existing TS5 schema and selected TS6 input checks in your browser. No account or card. Registration remains a free input tool; it is not included as a paid endpoint in the current prepaid offer. Automate the three available invoice, contract and event checks through the prepaid guide.

Developer start and integration kit · All billing countries

Existing subscriptions: recovery and API keys

Use existing subscription recovery for the previously accepted plan, save your private recovery code and continue to secure payment. No email sign-in is needed for this route. After payment is confirmed by the server, return with your code and create your API key. The code also lets you check access, manage billing and replace a lost key. Email sign-in is for existing business accounts. A payment return URL alone never grants access.

Existing assurance subscriptions only — separate scope

Developer, Integrator and Partner are usage tiers, not separate APIs. Guard, Watch/provider monitoring, Registration, deployment registry, Graph, Impact, Replay, Gate, Capsules, webhooks and the four Factory workflows share the organisation’s plan. Browse the technical catalogue and current availability.

Inspect before integrating

A read-only first request

This public endpoint does not need an API key. It reports the available evidence and missing capabilities, rather than granting an authorization decision.

curl --fail --silent --show-error \
  https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-assurance/v1/coverage

Existing assurance SDK and CLI

Installable client archives for Node.js 20 or later. Each includes its runtime dependencies, so installation does not require an npm account or registry download. These are direct Xynthera AI downloads.

Download the CLI archive, open a terminal in its folder and run:

npm install --offline --ignore-scripts --no-audit --no-fund ./xynthera-ai-cli-0.1.0-beta.3.tgz
npx --no-install xynthera-ai --help

For a JavaScript or TypeScript project, download the SDK archive and install it in that project:

npm install --offline --ignore-scripts --no-audit --no-fund ./xynthera-ai-eudi-0.1.0-beta.4.tgz
node --input-type=module -e "import { XyntheraAI } from '@xynthera-ai/eudi'; console.log(typeof XyntheraAI)"

Both clients support the four Factory workflows: release_gate, audit_export, source_impact and release_with_evidence. API calls require your organisation's Xynthera API key; keep it on the server.

Archive SHA-256 fingerprints
SDK: 7c8c05efa48b116fc3e334d1a2ed01d1cc52ce21879131961038fa488019d3f9
CLI: 4dc717d25e73a67ff3b21aef66c7896b1a43e11707b13899406650f9b040bae6

Compare your file using shasum -a 256 filename.tgz on Linux/macOS or Get-FileHash filename.tgz -Algorithm SHA256 in PowerShell.

Existing assurance subscription workflow

  1. For existing assurance access, inspect source coverage against your previously agreed scope.
  2. Recover your existing subscription and API key through its existing-access route. New customers use the prepaid guide for the three available checks.
  3. Register deployment and policy context, then use the Guard, Impact, Replay or Gate endpoints defined in the OpenAPI contract.
  4. Verify signed responses against the published keys, tenant/context and validity period before relying on them.
HTTP 200 does not mean “allowed”.

A Gate can return a signed DENY response with HTTP 200. Missing, expired or insufficient evidence must not be converted into approval by your integration.

Evidence and retention

For existing assurance subscriptions, retained receipts and Replay reports follow the accepted legacy terms. New prepaid checks store neither reports nor submitted documents; clients save their returned signed results. Export any evidence you need to retain under your own policy. Capsules contain signed references and context; they are not self-contained offline validation bundles.

Xynthera AI Registration performs input checks. It does not submit a legal registration, certify compliance or guarantee a registrar's acceptance.

Ask an integration question

Signed consistency and owner-controlled action APIs

Invoice arithmetic and reconciliation · Agent policy, approvals and atomic budget controls · MCP client connection. These beta capabilities share the existing Workbench allowance, with precise inputs and proof scope in the OpenAPI contract.