Options prop firm with integration

Every route, provider, and trust boundary in one directory.

Mayospell now runs a production v1 sandbox API beside its member trading routes. This directory shows exactly what is deployed, how identities and accounts stay isolated, why market data is degraded, and what remains before real brokerage routing can open.

Current integration status

Production sandbox online · live routing locked

The v1 contract, PostgreSQL ledger, API edge, event streams, credential controls, and public documentation are deployed. Self-service key issuance, healthy licensed market data, and brokerage execution are still gated.

Snapshot: August 22, 2026. Mayospell-owned sandbox API deployed; credential issuance and live-options routing remain gated.

Integration map

Five lanes, each with its own product truth.

A provider logo is not an integration contract. Each lane below names its actual access model, readiness, and claim boundary.

Lane

Provider

Access

State

Product truth

Member options workspace

Mayospell simulator

Signed member session

Working application routes

Returns one isolated simulated account, contract catalog, orders, fills, positions, P&L, and execution state. It never exposes the browser session to the simulator service.

Contract and price oracle

Tradier primary / Alpaca entitlement probe

Server-held credentials

Degraded provider authorization

The configured Tradier credential currently returns 401, while Alpaca option feeds return 403 without the required entitlement. The API stays online, but quote-dependent automation must stop until provider access is repaired.

Direct options provider desk

Alpaca paper account

Encrypted server cookie

Internal paper-adapter lane

Normalizes account, chains, bars, prints, orders, positions, fills, and quote streams for provider testing. It is not the public v1 sandbox ledger and is not Mayospell-funded live execution.

External options automation

Mayospell public API

Scoped Mayospell sandbox keys

Production v1 edge and sandbox core deployed; issuance is fail-closed

Mayospell owns and operates the API key, account, order, position, fill, market-data, audit, rate-limit, and resumable event contract. Live exchange routing still requires verified identity mapping, a broker/clearing adapter, licensed data, and reconciliation proof.

Options endpoint directory

Routes grouped by the trading job they perform.

The member simulator and provider-paper lane deliberately use different routes so account truth cannot be confused or silently crossed.

Member account truth

GET /api/options/workspace

Account, positions, orders, fills, timestamps, staleness threshold, and execution state

Boundary: Member session becomes an HMAC member key; raw identity never leaves Next.js

Contract discovery

GET /api/options/catalog?underlying=SPY

Approved OCC contracts and expiration catalog from the central contract service

Boundary: Underlying validation, no-store response, and no provider secret in the browser

Simulated execution

POST /api/options/workspace/orders

One accepted or rejected limit order tied to the signed member ledger

Boundary: UUID idempotency, max contracts, max debit, buy-to-open, sell-to-close, and two independent kill switches

Provider session

GET / POST / DELETE /api/options/session

Alpaca paper-account session state and verified data-feed probe

Boundary: Credentials remain server-side in an encrypted session; production requires a configured session secret

Provider market data

GET /api/options/expirations, /chain, /bars, /trades, /stream

Expirations, contracts, quotes, Greeks, premium bars, prints, and server-sent quote/trade events

Boundary: Authenticated provider session; stream falls back to snapshot polling and remains feed-qualified

Provider paper orders

GET / POST / DELETE /api/options/orders and /positions

Paper orders, cancellations, positions, and close requests

Boundary: Options approval check and server-side naked-sell block; not the funded simulator ledger

Provider audit state

GET /api/options/fills and /account

Normalized account approval, buying power, and recent fill records

Boundary: Authenticated session and explicit provider-source raw data envelope

Automation ownership

The integration contract includes who is responsible when it runs.

Mayospell, the trader, and eventual broker or data partners own different controls. The public product makes those lines visible before issuing a key.

Mayospell

Authenticate the member and enforce account ownership on every request.
Validate schemas, position effect, size, debit, and execution-switch state server-side.
Return timestamps, source labels, stale states, rejections, fills, and audit evidence.
Keep broker, oracle, database, and internal-service credentials out of browser responses.

Trader or developer

Run approved automation on personally controlled infrastructure.
Use idempotent client order IDs, bounded retries, backoff, and explicit timeout handling.
Treat stream disconnects and stale quotes as a stop condition, not permission to guess.
Keep strategies inside account, event, liquidity, expiration, and position-effect rules.

Broker and data partners

Define production execution, routing, entitlement, rate-limit, and market-data contracts.
Provide effective-dated fees, maintenance windows, incident escalation, and reconciliation records.
Authorize commercial display and redistribution before public options data is served.
Supply the evidence needed to distinguish paper, simulated funded, and real-capital activity.

Public API launch gate

Six proofs before sandbox becomes a live routing promise.

The public contract and sandbox service are real production surfaces. They are still not enough to promise automation against real capital without identity, commercial data, execution, and reconciliation contracts beside them.

1
Connect credential issuance to verified Mayospell member identity and explicit account mapping instead of an opaque browser session.
2
Contract a production options broker/clearing path and publish supported account ownership, instruments, strategies, and jurisdictions.
3
Obtain written OPRA and vendor authorization for commercial display, redistribution, professional users, and expected concurrency.
4
Publish the service-level support, deprecation, maintenance, incident, and reconciliation policy beside the deployed v1 OpenAPI contract.
5
Prove order idempotency, partial fills, cancel races, exercise and assignment, corporate actions, stream recovery, and reconciliation.
6
Run cost-aware sandbox, paper, and limited live certification with kill-switch and incident-response evidence before broad access.

Integration FAQ

What technical traders should verify before connecting anything.

These answers preserve the line between the working Mayospell sandbox, provider-shaped tests, and a supported public live API.

Does Mayospell have an options prop firm integration today?

Mayospell has a deployed public v1 sandbox API, working member routes for its isolated simulator, and internal provider adapters. It does not offer live brokerage execution or guaranteed capital allocation.

Can a trader run a bot against the options account?

The production v1 contract and sandbox trading core are online. New key issuance remains off until credentials bind to verified member identity and explicit account mapping. Existing approved sandbox keys can use the isolated ledger; live routing stays disabled.

Does the Alpaca sandbox prove production options capacity?

No. It proves contract normalization, account checks, quote and trade decoding, order workflows, and stream handling against a provider-shaped contract. Sandbox indicative data is modified or delayed and cannot prove public OPRA capacity or live fills.

How is one trader kept out of another trader's simulated account?

The Next.js server converts the signed member session into an HMAC member key. The private simulator maps that key to exactly one ledger and requires it on every workspace and order request; the raw browser session is never forwarded.

Inspect the connected surfaces

Follow the route from trading screen to operating evidence.

The integration story stays useful when every claim leads to a working product or a plainly labeled readiness surface.

The production sandbox API and documentation are available today. New credential issuance, live brokerage execution, Combine or Practice account mapping, and guaranteed capital allocation are not.