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

# Core Concepts

> The four objects that make up a ParlayX account, and how they relate.

Everything in ParlayX is built out of four objects. Understanding how they nest is enough to understand the whole product.

```text theme={null}
Organization
  └── Pod                    segregated book of capital
        ├── Wallet           on-chain venues execute through this
        ├── Credential tie   grants the pod use of an account-based venue
        └── Actor            a trader or bot, with its own API key
```

## Organization

Your company. The organization owns everything below it: the pods, the venue credentials, and the people and systems with access.

Venue accounts you connect — a Kalshi account, for example — are owned at the organization, because the account belongs to your legal entity and cannot be duplicated.

## Pod

A pod is a segregated book of capital. It holds its own balance, its own wallet, its own positions, and its own set of actors.

A pod is the unit you would otherwise create by opening another venue account. Use one per strategy, per desk, per client book, or per fund — whatever the thing is that you need funded and measured on its own.

<Card title="Pods in detail" icon="folder-tree" horizontal href="/pods">
  Funding, readiness, venue connection, and controls.
</Card>

## Actor

An actor is a trading identity: a person on your desk, or a bot. Each actor holds its own API key, and that key is minted for one specific actor-and-pod pairing. An actor trading in two pods holds two keys.

Actors are how you attribute activity. Every order carries the actor that placed it, so performance and exposure break down by trader without anyone sharing a login.

<Card title="Actors and permissions" icon="user-lock" horizontal href="/actors-and-permissions">
  What an actor can do, and how to take it away.
</Card>

## Credential

The thing that lets ParlayX act at a venue on your behalf. It takes two forms, depending on the venue:

|                  | Wallet venues                 | Account venues           |
| ---------------- | ----------------------------- | ------------------------ |
| Examples         | Polymarket                    | Kalshi                   |
| Identity         | A wallet, created per pod     | Your KYC'd venue account |
| Owned at         | The pod                       | The organization         |
| Reaches a pod by | Existing — one wallet per pod | Being tied to that pod   |

<Card title="Venues" icon="plug" horizontal href="/venues">
  How each venue connects, and what that means for separation between pods.
</Card>

## The rule that ties it together

**The organization owns. The pod operates. The actor attributes.**

Ownership sits at the top, because that is where legal and venue relationships live. Execution happens at the pod, because that is where capital and venue identity meet. Attribution happens at the actor, because that is who did it.<br /><br />Every permission question in ParlayX resolves at one of those three levels.