getapi

Stop Googling "how to get Twitter API key". Just run getapi twitter.

getapi is a CLI that walks you through setting up API credentials for popular services. Instead of hunting through documentation, signup flows, and developer portals, getapi gives you step-by-step interactive guidance and writes the credentials to your project when you're done.

Documentation: m2de.github.io/getapi

Quick Start

# Install
cargo install getapi

# Set up Twitter API credentials
getapi twitter

# Set up Stripe (writes to .env by default)
getapi stripe

# See all available providers
getapi list

Install

Homebrew

brew install m2de/tap/getapi

Cargo (from source)

cargo install getapi

npm (prebuilt binaries)

npx getapi-cli twitter

Binary download

Prebuilt binaries for macOS, Linux, and Windows are available on the GitHub Releases page.

Providers

getapi ships with 20 built-in provider recipes:

Usage

Basic setup

# Interactive setup for a provider
getapi <provider>

# Example
getapi openai

Commands

getapi <provider>       # Start guided setup for a provider
getapi list             # List all available providers
getapi resume           # Resume a paused setup session
getapi status           # Show active sessions

Options

--output <format>       # Output format: env, json, yaml (default: env)
--output-file <path>    # Write credentials to a specific file
--non-interactive       # Print steps without prompts (for CI/docs)
--recipe <path>         # Use a custom recipe JSON file

Manifest file

Create a getapi.toml manifest in your project to declare which providers your project needs:

[providers]
stripe = { output = ".env" }
openai = { output = ".env" }
supabase = { output = ".env" }

Then run getapi with no arguments to set up all missing providers.

For AI Agents

getapi is designed to work well with AI coding agents:

• getapi <provider> --help shows the full setup flow without running it
• getapi <provider> --non-interactive prints all steps as plain text, so an agent can relay instructions to a user or parse the credential requirements
• All provider recipes are JSON files in providers/ and can be read directly

Adding a Provider

The most common contribution is adding a new provider recipe. See CONTRIBUTING.md for the recipe JSON structure, step types, and testing instructions.

How It Works

1. Recipe files in providers/ define the step-by-step flow for each service as JSON
2. The runner walks the user through each step: opening URLs, prompting for input, offering choices, and validating credentials
3. Sessions track progress so you can pause and resume long setup flows
4. Output writes collected credentials to .env, JSON, or YAML files

Licence

MIT