Install Jentic One Beta

Connect the SpaceTraders API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SpaceTraders API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspacetraders.io%2Fspacetraders" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspacetraders.io%2Fspacetraders" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SpaceTraders API.

List Factions

Get Faction

My Agent Details

Accept Contract

Deliver Contract

Use Cases

Patterns agents use SpaceTraders API for, with concrete tasks.

GET STARTED

Start building with SpaceTraders API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

40 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using SpaceTraders API through Jentic.

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.

SpaceTraders API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer40 EndpointsREST

For Agents

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

Use for: I need to factions, I want to faction, Search for my agent details, Find all contracts

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

85%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

43%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SpaceTraders API to your agent

Capabilities

Use Cases

Start building with SpaceTraders API

Key Endpoints

Why Jentic?

Related APIs

FAQs

SpaceTraders API

Jentic AI Readiness Score

SpaceTraders API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness