RULE CHANGE
API capabilities
API capabilities article updated with changes to authentication and sandbox documentation reference.
What this means
The article now references Authentication and Sandbox as separate sections for CLI login procedures and test API key usage, whereas previously these topics were described inline. The functionality of CLI login creating browser-approved sessions and sandbox MCP calls accepting test API keys remains the same.
▸ View exact changes
What the page said before and after
Before Nov 2, 2026
API capabilities
− Source: https://docs.myfundedperpetuals.com/api-capabilities
Compare the public REST API and MCP tools with the trading website.
[!WARNING]
The developer API is in beta. Breaking changes may be introduced at any time.
Trading coverage
The public API can place and manage trades on existing challenge accounts.
It uses the website's paper execution engine and server-side trading rules.
It does not expose every website feature.
| Capability | Public API support |
|---|---|
| Account selection | List non-archived accounts accessible to the credential and read an account's risk snapshot. |
| Market discovery | List execution markets (optionally with alternate venues), inspect a market's availability, and request a quote with a size estimate. |
| Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders. |
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
shared request budgets.
MCP and CLI coverage
The REST methods in the MCP server and CLI are
derived from the REST specification. They do not add website capabilities
missing from REST.
MCP exposes the REST read and trading operations as tools. The REST
specification also contains two CLI authentication endpoints that MCP does not
expose as tools. Consult the endpoint reference for the currently available
fields and filters.
Live MCP access uses browser OAuth. Direct REST calls use an API key, while
CLI login can create a browser-approved session. Sandbox MCP calls accept a
test API key. See Authentication and Sandbox.
After Nov 11, 2026
API capabilities
Compare the public REST API and MCP tools with the trading website.
[!WARNING]
The developer API is in beta. Breaking changes may be introduced at any time.
Trading coverage
The public API can place and manage trades on existing challenge accounts.
It uses the website's paper execution engine and server-side trading rules.
It does not expose every website feature.
| Capability | Public API support |
|---|---|
| Account selection | List non-archived accounts accessible to the credential and read an account's risk snapshot. |
| Market discovery | List execution markets (optionally with alternate venues), inspect a market's availability, and request a quote with a size estimate. |
| Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders. |
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
shared request budgets.
MCP and CLI coverage
The REST methods in the MCP server and CLI are
derived from the REST specification. They do not add website capabilities
missing from REST.
MCP exposes the REST read and trading operations as tools. The REST
specification also contains two CLI authentication endpoints that MCP does not
expose as tools. Consult the endpoint reference for the currently available
fields and filters.
Live MCP access uses browser OAuth. Direct REST calls use an API key, while
CLI login can create a browser-approved session. Sandbox MCP calls accept a
test API key. See Authentication and Sandbox.
+ This documentation is built and hosted on Mintlify, a developer documentation platform.
API capabilities
− Source: https://docs.myfundedperpetuals.com/api-capabilities
Compare the public REST API and MCP tools with the trading website.
[!WARNING]
The developer API is in beta. Breaking changes may be introduced at any time.
Trading coverage
The public API can place and manage trades on existing challenge accounts.
It uses the website's paper execution engine and server-side trading rules.
It does not expose every website feature.
| Capability | Public API support |
|---|---|
| Account selection | List non-archived accounts accessible to the credential and read an account's risk snapshot. |
| Market discovery | List execution markets (optionally with alternate venues), inspect a market's availability, and request a quote with a size estimate. |
| Standard orders | Market, limit, chase, stop-market, stop-limit, take-market, take-limit, take-profit, and external conditional orders. |
| Limit instructions | IOC, FOK, and GTD; omit time in force for GTC. |
shared request budgets.
MCP and CLI coverage
The REST methods in the MCP server and CLI are
derived from the REST specification. They do not add website capabilities
missing from REST.
MCP exposes the REST read and trading operations as tools. The REST
specification also contains two CLI authentication endpoints that MCP does not
expose as tools. Consult the endpoint reference for the currently available
fields and filters.
Live MCP access uses browser OAuth. Direct REST calls use an API key, while
CLI login can create a browser-approved session. Sandbox MCP calls accept a
test API key. See Authentication and Sandbox.
+ This documentation is built and hosted on Mintlify, a developer documentation platform.