Recipes
All recipes

pokeapi

@jayjaychicago/pokeapi

by
@jayjaychicago
Revision
revision 1
Installs
0 installs
Published

Install it

Or run it in a terminal. It asks you a few questions, shows you what it is about to do, and stops for a yes or no before anything is created.

terminal
npx apiblaze install @jayjaychicago/pokeapi

That installs revision 1 — today's newest. To keep it from moving when the publisher pushes a new one, pin it: @1

npx apiblaze install @jayjaychicago/pokeapi@1

4 things this recipe asks you to agree to

These change who can reach your proxy, what it trusts, and what it can cost. Read them before you run the command.

  • upstreampokeapi.co

    every request — including your users' access tokens — is sent to this host

  • quota10,000 requests/daily

    requests above your current limit are billed to you

  • dev portalon

    creates a public page for this API

  • mcp serveron

    creates a public MCP endpoint for this API

The install command shows this list again and waits. Press enter instead of typing "yes" and it installs the recipe with your own current settings for everything above — which is still a working proxy. What each of these means

What it will ask you for

A name for the new proxy, then 2 values only you can supply:

  • Your own OAuth client IDoauth_client_id
  • Your own OAuth client secretoauth_client_secret

What this file cannot contain

No client secrets, no API keys, no users, no API keys of the publisher's consumers, no team or account identifiers. A recipe is built from an allowlist of fields, so anything not on that list was never read in the first place — and a recipe has no place to put a user in even if someone wanted to. How that is enforced

Read it before you run it

A recipe is one JSON file, and this one is public. Every setting, transform rule and route it will create is in there.

/api/recipes/jayjaychicago/pokeapi/1 · 8 KB

Or from the terminal: npx apiblaze show @jayjaychicago/pokeapi