API,
formalised.
One gateway, one set of conventions, a reference generated from the schemas that validate every request, and the guides to build against it.
curl https://api.rsx.group/example/v1/widgets/list \
-H "Authorization: Bearer rsx_live_..."Keys are issued from your RSX ID and shown once. Scopes are shaped like the URLs they unlock.
Conventions
Four things that hold on every endpoint, before you read any one of them.
One gateway
Every service answers on api.rsx.group behind one key, one rate limit and one set of headers. There is no second hostname to configure.
A fixed vocabulary
get and list are GET; add, update and remove are POST. Knowing one resource means knowing how to call the next one.
Errors are documented
Every failure is RFC 7807, and its type URL is a page here explaining what happened and what to do about it.
Specs, not screenshots
OpenAPI 3.1 is generated from the same schemas that validate requests, so the reference cannot drift from behaviour.
Services
Every service answers under its own prefix on api.rsx.group. Each page documents only that service's resources.
- 01exampleReference/template service: a widgets CRUD resource demonstrating every platform standard.v1Deprecated2 public scopes
- 02platformAPI key management: issue, scope, rotate, and revoke platform API keys.v1CurrentAdmin keys only
- 03idAccount and identity service: registration, login, sessions, and the platform's JWT issuer (JWKS).v1CurrentAdmin keys only
- 04webhooksGitHub App event receiver that relays repository activity (push, PRs, CI, releases) to Discord.v1CurrentAdmin keys only
- 05filesFile and media CDN control plane: uploads, share links, and object metadata for rsxcdn.com.v1CurrentAdmin keys only
- 06nodeControl plane for RSX-managed compute nodes: registration, desired state, and reported status.v1CurrentAdmin keys only
- 07statePersistent state and audit history for services that outlive the container they run in.v1CurrentAdmin keys only
- 08statusPublic operational state for RSX services: current status, uptime, incidents, and scheduled maintenance.v1CurrentAdmin keys only
- 09registrySoftware distribution for RSX-built packages: npm and Cargo packages, platform binaries, and OCI images.v1CurrentAdmin keys only
- 10projectsRSX's internal project and work management system: projects, work items, roadmaps, specifications, and the activity behind them.v1CurrentAdmin keys only
- 11accessControls who may install RSX applications and integrations, such as Roxy into a Discord server, and keeps the record of every decision.v1CurrentAdmin keys only
- 12aiAssistants for RSX systems: models with reasoning and read-only tools, knowledge of RSX's products, and operator-set tone and boundaries.v1CurrentAdmin keys only
- 13linkDevice identity for RSX Link: enrolling an installation with your RSX ID approval and a key it holds, listing your devices, and revoking them.v1CurrentAdmin keys only
Guides
How the platform works, written once and kept current. Edited live; what you read is the published revision.
Products, support, and every error.
Each RSX product has its own documentation, the support pages cover accounts, access and policies, and every RFC 7807 type URL the platform emits resolves to a page here.