API reference navigation

API Reference

Everything in Vamo is available over the API. Every endpoint below documents its access requirements, credit cost, and rate limits alongside its schemas.

The Vamo API is the control plane for GitHub developer search, enrichment, and outreach automation. Search for developers by what they have actually built, resolve GitHub or LinkedIn identities to full profiles, enrich them with contact data, and run automated outreach sequences.

Base URL

https://api.vamotalent.ai

Authentication

Every non-public endpoint takes a bearer credential:

Authorization: Bearer vamo_sk_...

API keys are prefixed vamo_sk_ and are scoped to one account. Mint and manage them with the Keys endpoints (POST /v1/keys, GET /v1/keys, rotate, revoke). Humans signed in to the Vamo app use session tokens over the same header; keys and sessions follow one usage model.

Status codes are precise: 401 no or invalid credential, 403 your role lacks the required entitlement, 402 your plan lacks the capability (upgrade), 429 a rate limit or usage quota is exhausted.

Credits and pricing

Operations are priced in credits from a pooled account balance. Every operation declares its own price, and the published spec carries it two ways: a machine-readable x-vamo block on each operation (access, pricing, rate limit, quota) and a one-line policy footer at the end of each operation description. Read your balance at GET /v1/account/credits and your allowances at GET /v1/quotas before spending.

GET /v1/pricing/catalog is public and free. It returns the plans, the dollars-per-credit rate (creditUsd), and the per-facet price table with what each facet gives you, so you can price a request before sending it. Facet prices there are read from the same catalog the biller charges from.

Rate limiting

Every endpoint declares its own fixed-window rate limit, scoped per account, per actor, or per IP. The exact limit and window are in the operation's x-vamo.rateLimit block. Exceeding a limit returns 429.

Quickstart

Resolve identity inputs to full developer profiles. An input is any human identifier: a handle, a GitHub or LinkedIn URL, a person's name, or a repo. You are billed 1 credit per input that resolves to a developer; ambiguous and not_found inputs cost nothing.

curl -X POST https://api.vamotalent.ai/v1/developers \
  -H "Authorization: Bearer vamo_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"inputs": ["torvalds"]}'

Authentication

Every request is authenticated with an API key passed as a bearer token. Create a key from your workspace settings, then send it in the Authorization header:

-H 'Authorization: Bearer vamo_sk_YOUR_KEY'

Explore

Deep research

Deep research: full-depth GitHub research on a developer, persisted as a report the whole account can read. Jobs run in rounds and report per-subject outcomes, so a partial result is a normal answer rather than an error.

Outreach

Contacts

Contact records for developers you are reaching out to. A contact carries no labels or tags: group contacts with projects and shortlists, which are the grouping primitives. There is no update endpoint either, so do not encode a grouping into a field like sourceDetail, which is provenance.

Outreach rules

Account-level rules that govern automated outreach.

Mailboxes

Connected sending mailboxes (OAuth grants) used by outreach.

Projects

Context

Project context entries: the facts and preferences that steer search and outreach.

Account

Identity

Who am I: the calling principal, its entitlements, and its quota allowances.

Members

Account members and roles.

Pricing

Public pricing: the sellable plans, the dollars-per-credit rate, and the per-facet price table. No credential required.

Credits

The credit balance, ledger, spending caps, and top-ups for the account.

System

Service health and status.

Other