Porter

Docs

Porter finds a public API, checks whether Guild can take it, and hands you or your agent one command that builds a private Guild integration draft on your own machine.

How it works

  1. Search for an API by name.
  2. Open a result. Porter fetches what Guild needs and checks it against Guild's importer.
  3. Hand the prompt to your agent, or run the command yourself. It uses your logged-in guild CLI.
  4. The draft is built and left private. You publish it, and connect credentials, when you are ready.

Finding your way around

  • Search

    Top right on every page, or the box on the home page. Type a product or domain; results come live from integrations.sh.

  • API page

    Opens from a search result. Make in Guild says whether Guild can take the API as-is, how it signs in, and gives the prompt or command that builds the draft.

  • Open in agent

    On an API page: opens Cursor with the prompt, or copies a one-line command for Claude Code, Codex CLI, or Gemini CLI.

  • Agent guide

    The Porter skill to copy, the MCP server, script flags, and what each run outcome means.

  • Guild Docs

    Guild's own integration docs, in a new tab.

What Porter supports

  • OpenAPI — Imports the spec's operations. API key, no auth, or OAuth 2.0.
  • GraphQL — Imports one graphql_query operation for the endpoint. API key or OAuth 2.0.
  • MCP — Points Guild at the server; Guild reads its tools. No auth, API key, or OAuth 2.0.

When an API cannot be imported as-is, its page says why instead of showing a command: for example a base URL with a tenant placeholder, or a spec that points at other files.

What Porter never touches

  • Your Guild login or token. The command runs on your machine with your guild CLI.
  • Provider API keys and OAuth client secrets. Those stay on your machine.
  • Publishing. Every draft stays private until you publish it.

For agents

Agents can use Porter through its MCP server on the Porter API, through a skill, or over plain HTTP. The agent guide has all three.