> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/agentops/venues-and-authority.md).

# Venues, accounts and authority

[← PAPER and evidence](/nytshift-docs/agentops/paper-and-evidence.md) · [Documentation home](/nytshift-docs/start-here/readme.md) · Next: [Product horizon →](/nytshift-docs/agentops/product-horizon.md)

NYTSHIFT is designed as one operating picture for supported perpetual-market context, not as one invisible pool of balances or permissions.

## Current venue picture

| Rail                | Current role                                                                                                          |
| ------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Arcus**           | Public perpetual-market context plus separately designed venue-specific authority boundaries.                         |
| **Lighter**         | Public perpetual-market context plus local PAPER simulation; no Lighter signer authority.                             |
| **Hyperliquid**     | Public market context plus independently gated signer integrations, including a separate policy-bound testnet path.   |
| **Robinhood Chain** | Read-only identity, provider, oracle and chain intelligence. It is not silently treated as a perpetual venue account. |

Availability is reported by the product for an exact route and evidence window. This table does not claim that every market, account function or signer path is live on every rail.

## The grouping model

| View            | State and boundary                                                                                     |
| --------------- | ------------------------------------------------------------------------------------------------------ |
| **All venues**  | **CURRENT.** Where reported, a derived summary with source labels and completeness state.              |
| **By venue**    | **CURRENT.** Where reported, the exact adapter boundary for each supported current venue.              |
| **By account**  | **CURRENT.** Where reported, one exact venue/account grant, never an ambiguous address merge.          |
| **By strategy** | **NEXT.** Positions and PAPER activity attributable to one version after the strategy registry exists. |
| **By operator** | **NEXT.** Human or agent attribution joined to the unified evidence model.                             |

“All venues” is a projection, not a new source of truth. A stale or missing venue remains stale or missing in the combined view. Collateral, margin rules, balances and execution authority remain venue-specific.

## One risk language, separate signer paths

AEGIS is the deterministic policy boundary. The control-plane ambition is to express risk in perps-specific terms such as exposure, slippage, freshness, collateral, leverage, liquidation distance, funding and venue health. The current implementation supports a narrower approved or rejected decision contract; the wider perps-semantic receipt API is **NEXT**.

No universal agent key sits above all venues. Any future capital-moving integration must independently prove:

* exact customer and account ownership;
* venue-specific credential custody;
* signer isolation;
* idempotency and one-attempt rules;
* authoritative order and fill reconciliation;
* stale-data and unknown-outcome handling;
* alerting, emergency stop and revocation;
* exact-release readiness evidence.

MCP deliberately publishes no submit, cancel, retry, sign, transfer, fund or withdraw tool.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nytshift.gitbook.io/nytshift-docs/agentops/venues-and-authority.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.