> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useasterisk.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Document only operations in the linked OpenAPI contract: the source-data ingestion operations and the source-scoped outbound webhook management operations.
> Treat the generated OpenAPI document as authoritative for request fields. Never invent compatibility fields, alternate endpoints, or additional source models.
> Preserve explicit nulls, decimal strings, timestamps, source identifiers, immutable version identifiers, and document-version links exactly as defined.

# Developer platform

> Understand the source-record resources available through Karsa's ingestion API.

Karsa's developer platform accepts versioned source records through one authenticated ingestion
surface. Use the Onboarding tab for a working first integration. Use this section when you need to
understand a resource, its identifiers, or how it connects to the rest of the platform.

## Platform components

| Component | What it represents | Start here |
| - | - | - |
| Customers and KYB | An individual or business, beneficial-owner relationships, and one business evaluation submission | [Customers](/concepts/customers) |
| Accounts | A bank, payment, or wallet account linked to a Customer | [Accounts](/concepts/accounts) |
| Documents | Immutable file content and source metadata | [Documents](/concepts/documents) |
| Transactions | A movement of value involving a known Customer, Account, or business | [Transactions](/concepts/transactions) |
| Outcomes | A result already recorded by your source system | [Outcomes](/concepts/outcomes) |

## The contract shared by every component

* Your source supplies a stable external identifier for each record.
* Karsa returns a stable `resourceId` for relationships and an immutable `versionId` for the exact
  observation it accepted.
* A changed observation appends a version; it does not overwrite history.
* `Idempotency-Key` makes retrying the same logical request safe.
* A KYB dossier pins the exact business CustomerVersion and evidence being evaluated.

Read [How records fit together](/concepts/source-schema) for the identifier graph and upload order.
Use the API Reference for authoritative fields, validation rules, and response schemas.

## Continue

<CardGroup cols={2}>
  <Card title="Customers and KYB" href="/concepts/customers">
    Model individuals, businesses, UBO Customers, and their relationships.
  </Card>

  <Card title="Accounts" href="/concepts/accounts">
    Link financial accounts to the Customers that own or use them.
  </Card>

  <Card title="Documents" href="/concepts/documents">
    Upload immutable evidence and reference its exact version.
  </Card>

  <Card title="Transactions" href="/concepts/transactions">
    Send money movement and connect it to known parties and accounts.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.