Skip to content

Legal

Terms of service

These terms cover your use of Cairva, a marketplace operated by Kordaen Venture Studio where buyers and suppliers negotiate and deliver AI inference service capacity. Each agreement you make on Cairva also has its own terms, and those govern the service it covers.

Working draft, pending legal review. This text describes how Cairva works today. It hasn't been reviewed by counsel and will change before general availability.

Last updated28 October 2026

  1. What Cairva is

    Cairva is a marketplace for inference service capacity. Suppliers list capacity and issue quotes. Buyers request terms, negotiate and accept. Cairva runs the workspace, the gateway that delivers and meters the service, and the operational checks around both.

    Cairva isn't an exchange. It doesn't issue tokens, securities or transferable credits, and it doesn't run a public order book.

  2. Lots and allocations

    • A lot is a time-bounded entitlement to a specific inference service, offered by a named issuer: either Cairva itself or a supplier Cairva has verified.
    • An accepted agreement gives the buyer organization access to that service on the agreed terms. It doesn't give ownership of hardware or of any other provider's account credits.
    • Lots and allocations are non-transferable. They can't be resold, assigned or moved to another organization.
    • A metered allowance is a token quota with rate limits. It doesn't include dedicated hardware or a minimum throughput unless the agreement says so.

  3. Agreements

    An agreement forms when a buyer accepts a specific quote version and the supplier countersigns it. The accepted version can't be edited afterwards. Pricing, volume, delivery window, rate limits, cancellation and under-delivery remedies are whatever that version states.

    Either party can cancel before the agreement becomes active. After activation, the agreement's own cancellation terms apply. Delivery problems are raised as disputes, which Cairva operations review against the metering records both parties can see.

  4. Payment and settlement

    Live agreements are settled by external invoice. The buyer pays outside Cairva and records the payment reference, and Cairva operations confirm the payment before the allocation activates. Cairva doesn't store card details or hold customer balances.

    Sandbox agreements carry no charge and are labelled as sandbox throughout the product.

  5. Using the gateway

    • API keys are bound to one allocation. Keep them secret. You're responsible for requests made with your keys until you revoke them.
    • Usage is metered from the provider's reported token counts. If a count isn't reported, the request is reconciled by operations from provider records rather than estimated.
    • Requests stop when the allowance is used or the delivery window ends. There's no automatic overage.
    • Use the service in line with the model's licence and the supplier's acceptable use terms, and don't use it to break the law.

  6. Suppliers

    Suppliers must be verified by Cairva before they can list available supply or issue quotes. By applying, a supplier confirms that the identity, capacity provenance and authorization evidence it provides are accurate, and that it's permitted to sell the service it lists.

  7. Service levels

    Cairva doesn't publish a platform-wide SLA at Genesis. Commitments about delivery belong to individual agreements and cover only what they state. Route health and incidents are reported on the public status page.

  8. Contact

    Questions about these terms go to privacy@cairva.xyz.

See also the terms of service, privacy policy and how Cairva works.