Claude Code+Faro

Give Claude Code the tools it doesn't ship with.

Generate images and video, add voice, scrape past anti-bot — then go where no chat app can: paid B2B contact and company data, and licensed third-party sources. All from one Bearer token.

Pay-as-you-go credits · Refunds on failure

~/.claude/env

Today

  • ANTHROPIC_API_KEY
  • OPENAI_API_KEY
  • DATAMERGE_API_KEY
  • TAVILY_API_KEY
  • APIFY_API_KEY
  • BRIGHTDATA_API_KEY

6 vendors · 6 invoices

With Faro

  • ANTHROPIC_API_KEY
  • FARO_API_KEY

2 vendors · 1 prepaid balance

Friction → Faro

Where Claude Code stalls, Faro picks it up

Four loud complaints from the Claude Code community in 2025–2026, paired with Faro's response.

The friction

No native image, video, or voice

Claude Code has no image generation, no video generation, and only a partial voice mode. The accepted workaround is “generate the prompt in Claude, then take it to ChatGPT.” Round-trips kill the flow.

Faro's answer

Image, video, voice — one call away

Search the marketplace by intent (“generate a product image”, “narrate this script”) and invoke the best fit. Faro fronts the upstream providers; you never touch their consoles or invoices.

The friction

WebFetch is summarized + anti-bot-blocked

WebFetch returns a model summary with a 125-character quote limit, so you can't extract full pages. cURL works on plain pages but most commercial sites block it — agents end up fabricating from search snippets.

Faro's answer

Paid data no chat app can reach

Web search and financial data, yes — but also B2B contact details, company firmographics, and licensed third-party datasets you can't get inside ChatGPT or Claude.ai at any price. All behind one Bearer, returned as raw structured results Claude can quote and reason against.

The friction

MCP setup is its own job

Each MCP server brings its own credentials, its own config, its own failure modes. If five engineers run Claude Code with five local MCP configs, there's no single source of truth — and tokens balloon per turn.

Faro's answer

One credential, no MCP plumbing

Talk to one HTTPS endpoint and one Bearer token. Add a capability by searching the marketplace, not by editing a config and restarting Claude. Same token on your laptop, your CI, and your teammates' machines.

The friction

Weekly limits make every call a gamble

Pro and Max users burn the weekly quota in hours, with no transparent metering. “I used it Friday, a little Saturday, 10 min Monday — hit the weekly limit” is a recurring refrain across the issue tracker.

Faro's answer

Pay per call, not per week

Prepaid credits, a displayed price per tool, and refunds on failed results. Every call has a known cost — not a debit against an opaque pool.

Quick start

Three lines from zero to invoking a tool

Use the faro CLI from your Claude Code shell, or call the REST API directly.

# one-time install (requires Python 3.11+)
pip install askfaro-cli
faro auth login    # paste your faro_ key

# inside any Claude Code session
faro search "generate an image of a coffee mug on a wooden table"
faro invoke <namespace>/<tool> --params '{"prompt": "coffee mug on a wooden table"}'
Full reference: CLI · REST · Quickstart · OpenAPI

In Claude's own session

Drop these prompts into Claude Code today

Each one is a single faro search + faro invoke away — no extra accounts, no extra keys.

Generate a 6-second product video of a violet aurora over a mountain at dawn

Resolved via google-veo

Get the latest news on Tesla's Q1 earnings

Resolved via brave-search

Scrape the pricing page at example.com and return the plans as JSON

Resolved via bright-data

Find a mobile phone number for the VP of Sales at Notion

Resolved via datamerge

Stop leaving Claude mid-task.

One account. One Bearer token. Every paid tool Claude needs to finish the job. Pay-as-you-go in credits.