For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/auth/oauth-authorization-server-metadata.md.
Authorization server metadata
RFC 8414 discovery. A remote MCP client fetches this to learn where to register and authorize, having been configured with nothing but the MCP server URL.
issuer must equal the origin this document is served from, which is
why it is mounted at the root rather than under /v1/auth. The
endpoints it names do sit under that base path; RFC 8414 does not
require them to share the issuer's prefix.
Served no-store: a client that cached this across a key or endpoint
rotation would fail in a way that looks like our outage.
The authorization server's published identity
application/json- response
issuer*stringEquals the origin this document is served from.
uriauthorization_endpoint*stringuritoken_endpoint*stringuriregistration_endpoint*stringDynamic client registration (RFC 7591).
urijwks_uri*stringuriscopes_supported*array<string>response_types_supported*array<string>grant_types_supported*array<string>code_challenge_methods_supported*array<string>S256 only; OAuth 2.1 drops "plain".
token_endpoint_auth_methods_supported*array<string>resources_supported?array<>RFC 8707 resource identifiers tokens may be minted for.
curl -X GET 'https://api.truemarkets.co/.well-known/oauth-authorization-server'{ "issuer": "http://example.com", "authorization_endpoint": "http://example.com", "token_endpoint": "http://example.com", "registration_endpoint": "http://example.com", "jwks_uri": "http://example.com", "scopes_supported": [ "string" ], "response_types_supported": [ "string" ], "grant_types_supported": [ "string" ], "code_challenge_methods_supported": [ "string" ], "token_endpoint_auth_methods_supported": [ "string" ], "resources_supported": [ "http://example.com" ]}Register an OAuth client POST
Dynamic client registration (RFC 7591). A remote MCP client — Claude, Meta Muse, MCP Inspector — calls this itself before starting an authorization flow; none of them can be handed a client_id out of band.
Accounts REST
Create the users your organization trades for, with their wallets, and read deposit details.