canonical: https://jentic.com/apis/railway.app/railway

# Railway App Railway API

Railway cloud hosting GraphQL API. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically execute graphql query. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Execute GraphQL query
- Access Railway API cloud infrastructure resources via REST API
- Query Railway API endpoints with structured JSON responses
- Authenticate requests with bearer credentials managed by Jentic
- Access Railway API resources programmatically via REST

## Use cases

### Cloud Infrastructure Operations

Use the Railway API to perform cloud infrastructure operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query.

Example prompt: Call POST `/graphql/v2` to execute graphql query

### Data Retrieval and Monitoring

Query Railway API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.

Example prompt: Query the Railway API API to retrieve current data and verify the response structure

### AI Agent Integration via Jentic

AI agents discover and call Railway 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 'execute graphql query', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/graphql/v2` | Execute GraphQL query |

## Key resources

- **GraphQL** — Operations related to GraphQL

## Why Jentic

- **Setup:** Wiring the Railway API by hand means learning its bearer auth and building your own client around a single GraphQL endpoint where every action is a query or mutation you have to compose. Through Jentic you install once, import the Railway API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Railway exposes one GraphQL endpoint (POST `/graphql/v2`), so scoping is operations-only: you limit the agent to the operations it needs, such as querying project and service state, rather than pinning it to a single resource in the URL. You choose which GraphQL operations it may run, so mutations you do not want are not included unless you add them.
- **Credential handling:** Your Railway 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 Railway projects' or 'trigger a deployment', and Jentic returns the matching Railway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Railway API use?

The Railway 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 execute graphql query with the Railway API?

Yes. Use the POST `/graphql/v2` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Railway 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 execute graphql query through Jentic?

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

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

The Railway API exposes 1 endpoints covering graphql operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Railway operations and credentials the agent can use. The Railway API is a single GraphQL endpoint (POST `/graphql/v2`), so scoping is operations-only: you choose which GraphQL operations the agent may run, such as read-only queries of project and service state, and you leave out any mutations you do not want it to call. Your bearer token stays stored encrypted in your instance and is injected only for the operations you have allowed.