One gateway, every tool, any agent

The pitch

The code you stop writing

You can call the vendor APIs directly, and for one agent against one service you probably should. Selat starts paying for itself at the third upstream, or the second agent, or the first time a refresh token rotates at 3am.

// a vault
await store.put(userId, 'github', encrypt(tok))

// a refresher, on a timer, forever
if (tok.expires_at < now()) {
  tok = await gh.refresh(tok.refresh_token)
  await store.put(userId, 'github', encrypt(tok))
}

// a client, a schema, an error shape
const gh = new Octokit({ auth: decrypt(tok) })

// then all of it again for Gmail, Drive,
// Discord, Notion, Slack

const res = await fetch(
  `${SELAT}/v1/tools/github__list_issues/call`,
  {
    method: 'POST',
    headers: {
      authorization: `Bearer ${SELAT_TOKEN}`,
      'content-type': 'application/json',
    },
    body: JSON.stringify({
      owner: 'vercel', repo: 'next.js',
    }),
  },
)

Getting started

Three steps to a first tool call

1. 01

   Sign in

   Google or GitHub. A workspace is created and one gateway credential is shown, once.

2. 02

   Connect an upstream

   From the dashboard, in a consent screen or a pasted key. OAuth, refresh and revocation are ours to carry.

3. 03

   Point your agent at the gateway

   The credential does not change when you connect or disconnect anything later.

curl -s https://api.selat.weekndlabs.com/v1/tools \
  -H "Authorization: Bearer slt_live_..."

curl -s -X POST https://api.selat.weekndlabs.com/v1/tools/github__list_issues/call \
  -H "Authorization: Bearer slt_live_..." \
  -H 'content-type: application/json' \
  -d '{"owner":"selat","repo":"selat","state":"open"}'

{
  "mcpServers": {
    "selat": {
      "type": "http",
      "url": "https://api.selat.weekndlabs.com/mcp",
      "headers": {
        "Authorization": "Bearer slt_live_..."
      }
    }
  }
}

Catalog

Upstreams

Only upstreams marked available can be connected today. The rest are in the catalog and not yet shippable, and the page for each one says so.

• githubAvailable

  Connect GitHub once and any agent can search repositories, read issues and file new ones through a single Selat credential. OAuth, refresh and pagination stay on our side.

• jiraSoon

  A hosted Jira tool surface for agents: search by JQL, read an issue, comment and transition, without an API token pasted into a config file.

• googleAvailable

  One Google grant backs the gdrive, gmail and gcal prefixes, so an agent lists a folder, reads a thread and checks a calendar without three separate consents.

• notionSoon

  Search a Notion workspace, read a page and append a block from any agent, with the workspace consent held once in the vault.

• slackSoon

  List the channels a workspace exposes, resolve who is in it, and post as the app, from a LangGraph node, an MCP client or a plain HTTP runtime, with one bearer for all three.

• linearSoon

  Issues, projects and cycles as agent tools, so a planning agent can read the board and file work back onto it.

Objections

What people ask before they try it

Why not a server per vendor?

You end up running one process per service, each with its own auth story, and your agent sees an unbounded tool list. Selat is one endpoint, one token, and a catalog you can filter.

Why not my model vendor’s connectors?

They work well inside that vendor. Selat runs the same tools against any runtime, including the one you wrote yourself, on your own hardware with your own OAuth applications.

What if the tool list gets huge?

Agents degrade well before any API limit, so the catalog is capped at 60 tools per workspace and every tool can be toggled. When the cap bites it says so, rather than quietly shortening the list.

Pricing

Priced on calls, not seats you forgot about

Every number here is read from the same plan table checkout uses, so a price on this page and a price on an invoice cannot drift apart.