canonical: https://jentic.com/apis/spacetraders.io/spacetraders

# SpaceTraders API

SpaceTraders is an open-universe game and learning platform that offers a set of HTTP endpoints to control a fleet of ships and explore a multiplayer universe. The API is documented using [OpenAPI](https://github.com/SpaceTradersAPI/api-docs). You can send your first request right here in your browser to check the status of the game server. Unlike a traditional game, SpaceTraders does not have a f. The API exposes 40 endpoints secured with bearer authentication.

## For AI agents

Programmatically list factions, get faction. Covers 40 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List Factions
- Get Faction
- My Agent Details
- Accept Contract
- Deliver Contract

## Use cases

### Developer Tools Operations

Use the SpaceTraders API to perform developer tools operations programmatically. The API provides 40 endpoints covering core functionality including list factions, get faction, my agent details.

Example prompt: Call GET /factions to list factions

### Automated factions Management

Automate factions operations by combining multiple SpaceTraders API endpoints. Agents can get faction and then my agent details in a single workflow.

Example prompt: Call GET `/factions/{factionSymbol}` to get faction, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SpaceTraders API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'list factions', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/factions` | List Factions |
| GET | `/factions/{factionSymbol}` | Get Faction |
| GET | `/my/agent` | My Agent Details |
| GET | `/my/contracts` | List Contracts |
| GET | `/my/contracts/{contractId}` | Get Contract |
| POST | `/my/contracts/{contractId}/accept` | Accept Contract |
| POST | `/my/contracts/{contractId}/deliver` | Deliver Contract |
| POST | `/my/contracts/{contractId}/fulfill` | Fulfill Contract |

## Key resources

- **factions** — Factions
- **fleet** — Fleet
- **contracts** — Contracts
- **systems** — Systems
- **agents** — Agents

## Why Jentic

- **Setup:** Wiring SpaceTraders by hand means registering an agent, carrying its bearer token on every call, and coordinating contract, ship, and system operations against the v2 host yourself. Through Jentic you install once, import the SpaceTraders API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SpaceTraders puts the ship symbol in the URL path (`/my/ships/{shipSymbol}/...`), so a rule can pin your agent to one ship: it can navigate, dock, or extract for that ship and nothing else. You choose the operations it may call, so state-changing ones like jettison or ship purchase are not included unless you add them.
- **Credential handling:** Your SpaceTraders bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my contracts' or 'navigate a ship to a waypoint', and Jentic returns the matching SpaceTraders operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SpaceTraders API use?

The SpaceTraders API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list factions with the SpaceTraders API?

Yes. Use the GET /factions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SpaceTraders API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list factions through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list factions'. Jentic returns the matching SpaceTraders API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SpaceTraders API have?

The SpaceTraders API exposes 40 endpoints covering factions, fleet, contracts operations.

### Can I limit what my agent is allowed to do with the SpaceTraders API?

Yes. Because you self-host Jentic One, your own rules decide which SpaceTraders operations and credentials the agent may use. Since the ship symbol sits in the URL path (`/my/ships/{shipSymbol}/...`), you can pin the agent to a single ship so it only navigates, docks, or extracts for that ship and nothing else. State-changing operations such as jettison or ship purchase stay out of reach unless you explicitly add them to the allowed set.