Legal & Compliance
Last Updated: October 13, 2026 | Effective Date: October 11, 2026
These Terms govern Kellian's developer surfaces — the API, MCP servers, webhooks, SDKs, embeds, and the agents built on them. The general Terms of Service apply too, including eligibility, sanctions, acceptable use, liability, and governing law; these control only where they speak to a developer question. Market outcomes follow the Market Resolution Policy. Creating a key means you agree to it.
Keys are issued conditionally and stay revocable. Keep them secret, tell us promptly if one is exposed, and expect us to segment access by identity, region, or risk. Every key carries scopes; a call outside them is refused.
Rate limits, and market-creation capacity, are published in the API's own responses and can change; a scope on your key is not capacity. Stay inside them, back off when told to, and do not circumvent them with extra keys. Availability of an endpoint today is not permission to use it — not in a jurisdiction, and not for a business model. We may suspend, throttle, gate, or retire any key, scope, route, or webhook at any time, so build for graceful degradation and do not promise users something that depends on one endpoint staying up.
Everything your integration trades, stakes, settles, or displays is denominated in Play Money (PM): play money with no monetary value — a balance on Kellian's own ledger, not a token — that cannot be sold, exchanged, redeemed, withdrawn, or transferred. Your interface is a surface we do not control, so this obligation is yours. In anything you publish — product, documentation, listing, or marketing — you may not:
If your integration shows balances or outcomes, carry the same disclosure Kellian does. We may require you to correct copy that does not, and copy that stays wrong is grounds for revoking access.
You are responsible for everything done through your keys and agents — prompts, market wording, sources, and transactions — whether a human typed it or a model generated it. "The model wrote it" is not a defence. Markets you create must be clear, objectively settleable, lawful, and not misleading.
If you serve end users, their eligibility checks, region and sanctions screening, disclosures, support, and complaints are yours. You may not route prohibited activity to restricted users, conceal end-user geography, or help anyone in a comprehensively sanctioned jurisdiction reach the service. Do not imply that Kellian is the seller, author, guarantor, or insurer of your service or your markets. We may reject, label, delay, freeze, delist, or investigate content and keys without taking on your responsibility.
Access is a limited, revocable licence to build on Kellian, not a grant of rights in our data or systems. Reach the service only through documented interfaces; do not scrape it, republish bulk data, or use it or its outputs to build or train a competing product, dataset, or model. Do not reverse engineer components we have not open-sourced, except where the law says you may. Do not strip attribution, provenance, or rate-limit signals — we embed them, and read our logs and abuse signals to secure the platform and evidence misuse. If your integration handles personal data, its privacy compliance is yours.
DEVELOPER SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE." WE DISCLAIM ALL WARRANTIES, INCLUDING ACCURACY, AVAILABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND COMPLIANCE SUITABILITY.
You will indemnify Kellian and its people against claims arising from your integration, your users, your markets, your content, your marketing, or your legal failures. To the maximum extent permitted by law, our total liability for the developer services is limited to what you actually paid us for them in the twelve months before the claim arose. Questions: [email protected].