Servicegraph

servicegraph

Overview

The generic way to drive ServiceGraph — a platform of metrics-enriched business datasets for founders: where to launch, who to email, who to hire. Use this skill when the user explicitly reaches for ServiceGraph. For intent-first asks that don't name the brand ("find me a CPA firm"), a specific find-* skill is the better fit — defer to it.

There is no single global catalog, and this skill hardcodes nothing about the data. It discovers everything through the API at runtime, so it stays correct as datasets are added, renamed, or re-priced. Discover the datasets from the API, discover each dataset's schema and filters from the API, then search and unlock against it. Never assume a dataset id, a field name, or a price — ask the API.

Prerequisites

• ServiceGraph access, either:
  • the ServiceGraph MCP server (https://mcp.servicegraph.co) loaded in your harness — this plugin's .mcp.json wires it up; OAuth handles credentials in the harness sandbox, no token enters the model context — or
  • a ServiceGraph API key (vk_…, minted at https://servicegraph.co/profile/api-keys) available as SERVICEGRAPH_API_KEY for the REST path (see Auth below).
• An HTTP client for the REST path — Bearer-auth with the vk_… key.

Two ways to call

Both speak to the same backend; use whichever your harness has.

• MCP server (preferred when loaded) — https://mcp.servicegraph.co, tool names contain servicegraph. OAuth handles credentials in the harness sandbox; no token enters the model context.
• REST — https://api.servicegraph.co, any HTTP client, Bearer-auth with a vk_… key. The universal fallback.

How it works

Everything except unlocking is free — discover, inspect, validate, and browse as much as you like; only revealing detail costs credits.

Capability	MCP tool	REST	Cost
Find what datasets exist (ids, sizes, prices)	list_datasets	GET /v1/datasets	free
Discover a dataset's schema + filter fields	describe_dataset, list_fields, list_field_values	GET /v1/datasets/:id…	free
Build & validate a filter (or draft one from plain English)	check_filter, translate_intent	…/check, …/translate-intent	free
Search → free brief rows (identity + headline metrics)	search_dataset	…/search	free
Read an already-unlocked row	get_row	GET /v1/datasets/:id/:apex	free
Unlock rows → reveal contacts + full metrics	unlock_rows	POST …/unlocks	spends credits
Check credit balance	get_credit_balance	GET /v1/me/credits	free

The shape is always the same: discover datasets → discover the dataset's schema → search free briefs → unlock the rows the user picks. Rows are keyed by apex domain (stripe.com, not a full URL). Confirm field and value names against the API before trusting a zero-result search — the filter parser accepts invented values silently.

Auth (REST path)

Keys are vk_* tokens the user mints at https://servicegraph.co/profile/api-keys (free credits on signup). The MCP path needs none of this.

Keep the token out of the model context — never read .env/credential files into context, and route authed calls through a shell wrapper so the key flows from the environment into the Authorization header. On 401, ask the user to set SERVICEGRAPH_API_KEY (env or .env.local) and retry; don't accept the key pasted into chat.

Cost & confirmation

Only unlock_rows spends credits, at the per-row price the dataset reports — read it, don't assume it. Unlocks are atomic (a 402 charges nothing) and cached for the dataset's TTL (re-unlocking within it is free). Confirm the cost with the user before unlocking a batch, and check get_credit_balance first if it's large.

Output

All responses are JSON.

• Dataset discovery (list_datasets / GET /v1/datasets) returns each dataset's id, size, and unlock pricing — read those, never assume them.
• Search returns free brief rows keyed by apex domain — identity plus headline metrics — with a per-row unlock hint and the match total.
• Unlock (unlock_rows / POST …/unlocks) reveals a row's gated detail — contacts plus full metrics — at the per-row price the dataset reports, cached for the dataset's TTL.
• Credit balance (get_credit_balance / GET /v1/me/credits) returns the current balance.

Errors

• 401 on the REST path — the key is missing or invalid. Ask the user to set SERVICEGRAPH_API_KEY (env or .env.local) and retry; never accept the key pasted into chat.
• 402 on unlock — balance is short. Unlocks are atomic, so nothing was charged; report the shortfall and check get_credit_balance.
• Zero-result searches — the filter parser accepts invented field and value names silently. Re-confirm names via list_fields / list_field_values before trusting an empty result.

Examples

"What datasets does ServiceGraph have?" list_datasets (or GET /v1/datasets) → present each dataset's id, size, and unlock price. Free.

"Search ServiceGraph for design agencies in New York and unlock the top 3." Discover the matching dataset (list_datasets), inspect its schema (describe_dataset / list_fields), validate a filter (check_filter), search_dataset → present the free briefs, confirm the unlock cost with the user, then unlock_rows on the three chosen apexes.

Resources

• Upstream source: https://github.com/nostrband/ServiceGraph
• ServiceGraph API: https://api.servicegraph.co — keys at https://servicegraph.co/profile/api-keys
• Specific skills in this plugin (find-law-firm, find-marketing-agency, find-pr-agency, …) — prefer them when the user states an intent without naming ServiceGraph.