Skip to main content
Developer resources

Railen AI developer resources

Railen integrates an AI sales agent with a dealership website, live inventory, lead delivery, and the store workflows configured during onboarding. These resources are for dealership technology teams, agencies, integration partners, and AI clients that need the supported machine-readable entry points.

The public API surface is intentionally limited to discovery and status. The production integration interface is the authenticated Railen MCP server documented below. Dealership and partner integrations are provisioned for an authenticated account so inventory, shopper, appointment, and CRM data remain scoped to the correct organization.

Public discovery API

Railen publishes a small, read-only HTTP API so agents can discover the official documentation, OpenAPI contract, agent index, and MCP server card without scraping the site. It does not expose dealership inventory, shopper conversations, appointment data, CRM delivery, account settings, write operations, webhooks, or anonymous credentials.

curl https://railen.ai/api/v1/status
curl https://railen.ai/openapi.json
curl -H "Accept: application/linkset+json" https://railen.ai/.well-known/api-catalog

Model Context Protocol server

The Railen MCP server uses Streamable HTTP and requires authentication before protected tools can be listed or called. MCP clients should begin with the server card on the Railen website, connect to the declared remote endpoint, and follow the authentication challenge returned by the server.

Streamable HTTP endpoint
https://mcp.railen.ai

Versioning and deprecation

The public API is versioned in the URL path. A breaking change ships as a new version rather than altering an existing one, so a client pinned to a path keeps the contract it integrated against.

Deprecation
Present once a version is deprecated. Carries the date the deprecation was announced.
Sunset
Present alongside it. Carries the date the version stops responding, per RFC 8594.
Link; rel="successor-version"
Points at the version that replaces it.

Railen gives at least 12 months between a Sunset header first appearing and the version being withdrawn. Neither header is present today: nothing is deprecated, and publishing one that is not true would be worse than publishing none.

Structured errors

Unknown public API routes return application/problem+json with a stable code, human-readable detail, and a resolution hint so agents can recover by reading the OpenAPI document or API catalog instead of parsing an HTML 404 page.

curl https://railen.ai/api/v1/orank-probe-test

Integration scope

A Railen onboarding connects the dealership inventory source and the configured lead-delivery destination. CRM-ready appointments can be delivered as tagged ADF/XML leads, while website, email, and SMS experiences are enabled only for the dealership and channels included in that account. Exact credentials, tenant identifiers, and test procedures are supplied privately during onboarding and must not be placed in public client code.

Integration support

For MCP access, a dealership integration, or an agency deployment, email [email protected] with the dealership group or partner name and the integration you are evaluating. There is no anonymous production access and no public credential to copy from this page.