AGENT / OAUTH

Connect with a native MCP connector

Use a supported native MCP connector when your client offers one. It uses OAuth, so you do not provide a provider key or download a CLI; you still approve access once in your browser. Availability is not promised for every account or hosted chat product.

Use a supported native MCP connector to add https://relaylane-ebgvfhzs.manus.space/mcp, then choose OAuth. After I sign in and approve, only discover and inspect available tools; do not run a tool or spend money. If no connector permission is available or the network is denied, stop and report that limitation accurately. Do not ask a hosted chat product to download a CLI by default. Read https://relaylane-ebgvfhzs.manus.space/en/SKILL.md only for the supported setup details.

Apps connected to your account. →

Prefer commands? · CLI

Download the versioned CLI, then run setup. Node.js 20 or newer is required. Setup only pairs and checks your connection; it does not dispatch a model request.

curl -fSLo relaylane-cli.mjs https://relaylane-ebgvfhzs.manus.space/downloads/relaylane-cli-1.1.0.mjs
node relaylane-cli.mjs setup --client "AI-agent" --locale en

Verified API gateway · controlled trial

One connection. More capable agents.

Give your agent one connection for public data and text generation. Copy the setup instruction, approve pairing once, then discover, inspect and run verified tools.

Try the gateway ↗Inspect the tool contract →

Verified APIs are available under shared daily trial limits. Untested and failed candidates cannot execute. Live paid execution and native MCP OAuth remain unavailable.

RELAY / TOOL GATEWAYControlled trial

discover → inspect → run

POST /v1/inspect

{
  "endpoint": "relaylane#text.generate"
}

→ input schema
→ daily trial limits
→ MCP + REST

A SMALLER INTEGRATION SURFACE

From task to tool, without the setup maze.

For the current trial, model credentials stay on the server. You sign in to RelayLane and use one RelayLane key. Private-account access will still require separate consent.

01
Discover
Find tools by what they can do, not by the name of an API provider.
02
Inspect
Review inputs, availability, access requirements and a clear price before a call.
03
Run
Run with a RelayLane key, an idempotency key and a daily trial limit. Read the actual output and usage; no paid wallet is offered.

Built for people. Described for agents.

15 launch languages

Full public onboarding in Japanese, Korean and major European languages. Interface language does not imply verified local data-provider coverage.

Machine-readable contracts

Stable tool IDs, versioned input schemas, explicit availability and honest discovery metadata.

Pick the connection your product already uses.

No separate provider key is required for verified managed and public-data trial tools. Pair your agent once or use one RelayLane key.

MCP

MCP client

Add the HTTPS endpoint and a Bearer RelayLane key to a client supporting Streamable HTTP and custom headers.

↗

REST

Application API

Discover, inspect and run with stable JSON contracts. Poll a run without resubmitting it.

↗

TOOLS

Tool-calling model

Load three compact function schemas. Your own application executes returned tool calls through RelayLane.

↗

SKILL

Agent instructions

Read the localized SKILL.md. It describes real capabilities, limits and the exact execution flow.

↗

MCP key authentication is available; OAuth-only clients need the REST bridge. Client support must be checked in your own product.

Start with a useful job.

Public-source research

Find authorized public company, financial, book and development data, then synthesize it with source attribution.

Explore this workflow →

Localized marketing

Draft multilingual content from an approved brief, with review before publishing.

Explore this workflow →

Before you connect

Do I need to register with every API provider?

Not for the current managed tools and public-data trial. You authorize one RelayLane account. Private-account APIs will still need separate permission.

Are thousands of external APIs already connected?

No. Check the live registry for the current verified and executable counts. Candidates and different access protocols are not counted as working APIs.

Can every large-model product use this?

Use REST from an application, MCP from a compatible client, or function schemas from a tool-calling model. Some hosted clients do not accept custom MCP headers.

Will search engines or AI products find this automatically?

Public HTML, sitemaps and machine-readable documents make discovery possible. They do not guarantee indexing or recommendation.

Control is part of the connection.

For the current trial, model credentials stay on the server. You sign in to RelayLane and use one RelayLane key. Private-account access will still require separate consent.

Credentials stay server-side

Provider credentials remain on the server and never appear in agent prompts or browser code. RelayLane keys are hashed and revocable.

Access follows the task

Platform-managed tools and user-authorized private data are separate. No broad account access is implied.

Costs before calls

All API trials share account and platform daily limits. Stripe test credits are isolated; live paid execution is not enabled.

RELAYLANE

Which API should we connect next?

Tell us the first job your agent should be able to finish. Your request helps us prioritize real integrations.

Contact consent and advertising consent are separate. Contact requests are stored for follow-up. Advertising attribution is optional; no Google or Meta pixel is active.

Privacy and data use — RelayLane →