Pinme Llm

If you're building Workers on PinMe's platform and need to call LLMs through OpenRouter, this skill walks you through the proxy setup so your code never touches the real API key. It covers the models endpoint, chat completions with streaming support, and how to wire up OpenRouter's web search tool through the completions API. The examples are TypeScript heavy and show both non-streaming and SSE passthrough patterns. Useful when you're wiring up AI features in a PinMe Worker and need to understand the environment variables, query string requirements, and error codes that come back from their proxy layer.

skills.sh installs: 503
GitHub stars: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add glitternetwork/pinme --skill pinme-llm --agent claude-code

Installs into .claude/skills of the current project.

Files

PinMe Worker OpenRouter API Integration

Guides how to call PinMe platform's OpenRouter proxy APIs in a PinMe Worker (TypeScript). Workers use the PinMe project API key; they never hold the real OpenRouter API key.

Environment Variables

The following environment variables are automatically injected when the Worker is created — no manual configuration needed:

// backend/src/worker.ts
export interface Env {
  DB: D1Database;
  API_KEY: string;       // Project API Key from create_worker
  PROJECT_NAME: string;  // Actual project_name from create_worker; must match API_KEY
  BASE_URL?: string;     // Optional override for PinMe API base URL, defaults to https://pinme.cloud
}

API_KEY authenticates the Worker to PinMe. PROJECT_NAME is required for chat/completions and must belong to the same project as API_KEY. When BASE_URL is not set, use https://pinme.cloud.