Skip to content
Agentmart
Submit a tool

sprite-api-gateway

Use policy-controlled Sprite Connectors for GitHub, OpenRouter, and custom HTTP APIs without exposing provider tokens.

Skill by superflyOfficial

IndexedMIT★ 5
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/superfly-sprite-api-gateway

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use policy-controlled Sprite Connectors for GitHub, OpenRouter, and custom HTTP APIs without exposing provider tokens. Use when an agent running commands inside a Sprite needs an external API.

Use cases: backend, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/sprite-api-gateway

What's inside

Skill name
sprite-api-gateway
Description
Use policy-controlled Sprite Connectors for GitHub, OpenRouter, and custom HTTP APIs without exposing provider tokens. Use when an agent running commands inside a Sprite needs an external API.
License
MIT
Instructions
29 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Sprite API Gateway

Gateway requests must originate inside a running Sprite. Do not call the gateway from the local Pi process unless its shell tools are currently routed to a selected Sprite.

## Discover connectors

Run inside the Sprite:

```bash
curl -sS https://api.sprites.dev/v1/gateway/list
```

Use the returned `gateway_base_url` and provider-specific usage snippet. Do not guess connector IDs or gateway paths.

If a provider is available but not configured, give the user the returned `setup_url`. If scopes are insufficient, give the returned `request_scopes_url`. Never ask the user to paste the provider token into the Sprite.

## Calling a connector

The gateway URL has this form:

```text
https://api.sprites.dev/v1/gateway/<provider>/<connection-id>/<provider-path>
```

Do not add the provider's authorization header. The gateway authenticates the calling Sprite and attaches the stored credential after evaluating connector access policy.

Treat `403` as a policy or endpoint restriction, and `401` as evidence the call did not originate from a valid Sprite. Do not weaken policy automatically.

From superfly/pi-sprites, MIT.

More from superfly/pi-sprites

Compare and alternatives

    Featured in

    Signals

    Stars
    5
    Forks
    1
    Open issues
    0
    Last commit (this folder)
    Aug 6, 2026 (2 months ago)

    From GitHub (fetched Oct 24, 2026).

    Details

    License
    MIT
    Repository
    github.com/superfly/pi-sprites
    Website
    sprites.dev
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026
    Source
    GitHubgithub-graphql

    More from superfly

    Cite this page

    sprite-api-gateway skill. Agent Mart. https://agentmart.dev/skills/superfly-sprite-api-gateway (last updated 2026-10-24)