pokeapi

PokéAPI — Plasm CGS Schema

A Plasm domain model for PokéAPI (v2). Large entity surface: Pokémon, moves, abilities, items, locations, generations, and more.

CLI / REPL

cargo run --bin plasm-repl -- \
  --schema apis/pokeapi \
  --backend https://pokeapi.co

# One-shot JSON (live HTTPS)
plasm-cgs --schema apis/pokeapi --backend https://pokeapi.co \
  --output json pokemon pikachu

No API key is required for the public service.

HTTP execute (plasm-mcp --http)

Multi-entry catalogs: just build-catalogs then --catalog-dir target/plasm-catalogs (each packed catalog corresponds to an apis/<name>/ tree). PokéAPI’s default HTTP origin is http_backend in domain.yaml.

plasm-mcp --http and --mcp require a strong JWT secret for auth-framework initialization (see AGENTS.md). Example:

export PLASM_AUTH_JWT_SECRET='<long random string>'
just build-catalogs
cargo run -p plasm --bin plasm-mcp -- --catalog-dir target/plasm-catalogs --backend http://localhost:1080 \
  --http --port 3001 --mcp --mcp-port 3000

1. POST /execute with {"entry_id":"pokeapi","entities":["Pokemon"]} → 303 + Location.
2. GET that URL for prompt, session, prompt_hash.
3. POST the same path with a Plasm line body. For a get-by-name, use Pokemon(pikachu) (same meaning as CLI pokemon pikachu). Plasm does not use a Get(…) wrapper or Entity:slug — those shapes are parse errors or invalid; Entity(id) is the only get-by-id form. Prefer Accept: application/json when you want structured rows.

Expression forms are validated against the teaching table prompt for that session; if a line fails to parse, the API returns a problem+json error.