# Frequently asked questions

## What does KlineO do?

KlineO helps teams study token liquidity, compare plans, review evidence, and prepare decisions around issuer liquidity and treasury workflows. The application combines public project observations with private workspace records, deterministic studies, human review, policy boundaries, and reporting.

Execution is a separate, gated capability. A study, score, recommendation, or saved decision does not itself move funds.

## Who can use these docs and SDKs?

The documentation is for public developers, issuer teams, analysts, and integration partners. Reading the docs does not require an account. Private API operations require credentials and authority for the relevant organization. Some public endpoints are read-only and have their own request limits and supported-input boundaries.

## Which SDKs are available?

The current source contains a TypeScript client, `@klineo/liquidity-os-sdk`, and a Python client, `klineo-liquidity-os`, imported as `klineo_liquidity_os`. Both SDKs use version `2.1.0` and target API v2, whose OpenAPI contract version remains `2.0.0`. The current contract contains 238 operations and 332 schemas. Follow the SDK's installation guide for an actual published artifact or repository checkout.

SDK 2.1.0 adds partner preparation receipt recovery and its response types relative to SDK 2.0.0. API and SDK versions are separate: this update keeps the API base path `/api/liquidity-studio/v2` and does not enable a disabled deployment capability. Read the [changelog](/resources/changelog/) before upgrading.

The standalone TypeScript SDK declares Node.js `>=22.18`. The Python package requires Python `>=3.11`. The application repository's tooling has its own Node.js version range; it is separate from the standalone SDK's runtime requirement. Package availability and installation instructions belong to the associated SDK release; the existence of a package name does not prove registry publication.

## Which API URL should I configure?

Use the API origin assigned to your environment followed by `/api/liquidity-studio/v2`. For example, a deployment at `https://your-api.example` uses `https://your-api.example/api/liquidity-studio/v2`.

The documentation host is not the API host. Do not use `docs.klineo.io` as an API base URL unless an operator explicitly supplies that configuration. The underlying Studio v1 API is a separate prefix.

## How do I get API access?

Use your authorized workspace administrator or KlineO support to arrange organization membership and permitted credentials. Developer credentials and OAuth clients require provisioning and appropriate scopes. A token is bound to its permitted organization and operations; possessing a token does not establish permission to use every method in the client.

## Can I place a service credential in a browser application?

Keep API keys, OAuth client secrets, and service tokens on a trusted server. Use a backend integration to call the SDK and expose only the data your frontend needs. The Studio application's interactive session has a separate authentication flow; it should not be replaced with a shared service secret.

## Why does a visible feature return unavailable or blocked?

The UI and API contract can describe a capability while its deployment lacks an enabled provider, supported source data, completed study, applicable permission, or signed release. Inspect the structured error and environment status. Repeatedly retrying cannot satisfy a missing release gate.

`GET /api/liquidity-studio/v2/status` separates API storage availability from `release.authorityEnabled` and feature rollout. Studio v1 status additionally reports runtime, automation, and funding permission.

## Is demo data real market or customer data?

Labeled demo and sample views use illustrative records. They demonstrate navigation and workflows; they do not establish a live balance, verified project ownership, actual execution, completed customer investigation, or release approval.

Connected views depend on returned server evidence. Check source timestamps, finality, coverage, and unavailable reasons before relying on an observation.

## Does a public project observation prove issuer ownership?

No. A supported public identifier can resolve a project token and supported pool observation without account ownership. Project-control verification and private custody evidence are separate workflows with their own authority and source requirements.

## Does an investigation answer every question about a project?

No. Review its question, scope, coverage, referenced observation, and limitations. Public-evidence and research workflows can retain partial coverage. A broader question entered in a Decision Pack does not enlarge the evidence actually gathered by an attached investigation.

## What is a Decision Pack?

A Decision Pack is a private, versioned record of evidence and human review. It can record a question, assumptions, supporting investigation or scenario references, a rationale, and a follow-up. It does not publish content, authorize a payment, verify ownership, or sign a transaction.

## Can a treasury scenario be treated as current spendable cash?

No. A declared historical scenario preserves its source cutoff and assumptions. Even a finalized signed custody observation does not, by itself, establish unrestricted funds, complete obligations, or expense coverage. Follow the evidence, reconciliation, classification, and current-authority requirements for the specific workflow.

## Are simulation results predictions or guarantees?

Results describe the supplied scenario, engine version, source lineage, and inputs. They are comparative model evidence. Review assumptions, warnings, path count, units, and complete input snapshots where available. Historical observations and modeled outcomes cannot guarantee future liquidity, returns, or execution quality.

## What do atomic amounts and pips mean?

Atomic amounts are integer token units represented as strings to preserve precision. Interpret them using the token's recorded decimals. In the v2 contract, pips are parts per million: `1,000,000` equals `100%`, so `10,000` pips represent `1%`. Respect each field's schema and bounds; do not convert every financial field to a floating-point number.

## Can the SDK sign or submit arbitrary transactions?

The generated SDK is an HTTP client. It does not hold issuer Safe keys, sign issuer transactions, or grant execution authority. Issuer Safe approvals, typed adapters, policy checks, simulation, timelocks, caps, and signed runtime releases remain separate boundaries. Arbitrary targets, arbitrary calldata, and AI execution are disabled in the committed v2 release manifest.

## Which networks are live?

The committed configuration targets BOT testnet `968` and includes BOT mainnet `677` types. The committed manifests disable live rollout on both. Supported public read-only analysis can use a different chain, such as a configured Base observation; that observation does not bind an execution environment.

Read the actual deployment status and accepted release evidence for live availability. A chain ID in a package, UI default, or roadmap does not prove a deployment is authorized on that chain.

## How should I handle concurrent writes?

Where required, send the exact current resource version using strong `If-Match` and a unique idempotency key for the intended command. On a concurrency conflict, read the resource again and re-evaluate the change. Retry an identical uncertain command with the same key; create a new key when you change the command. The SDK exposes these request fields but does not decide whether an application should retry.

## How should I report an API problem?

Contact [KlineO support](mailto:support@klineo.xyz) or your authorized operator. Include the SDK/version, environment, operation, response status, error code, and correlation ID when present. Provide a small redacted reproduction. Keep tokens, passwords, private keys, customer data, and unredacted private evidence out of the report.

No response-time or uptime guarantee is established by this documentation. An agreed commercial support arrangement, if any, governs its own terms.

## Is the product independently audited or production approved?

The source implements audit and release evidence gates. That is different from a completed independent audit or an accepted production release. Check the published review artifacts and exact accepted release evidence for the environment you intend to use. The committed templates leave approval evidence empty and activation disabled.

## Where can I see what is changing?

Read the [changelog](/resources/changelog/) for the documented contract baseline and the [roadmap](/resources/roadmap/) for intended milestones. Plans have no committed calendar launch dates here. The actual release status and repository artifacts remain the sources for enabled behavior.