Growth hacking on autopilot, with an API.
54 capabilities over MCP, REST, and CLI. Scored conversations, the people behind them, the AI answers you are missing from.
Fed a list, an agent messages strangers. Fed Oetzi, it shows up where people are already asking.
Quotes before it spends. Logs what it sent.
claude mcp add --transport http oetzi \ https://www.oetzi.ai/api/mcp \ --header "Authorization: Bearer oetzi_…"
> capabilities_search "people who liked a post" pull_engagers · list_people · get_person > pull_engagers lead_id=8c83… dry run · estimate 1 credit · 15 likers, 3 reposts > pull_engagers lead_id=8c83… approved max_credits=1 job 5d03… → 15 people, 12 new · 1 credit spent > record_outreach person=2bc5… channel=x_dm outcome=sent ok · the graph knows they were touched
scoped keys
read, write, spend, post. A key does only what you let it.
dry-run first
Every paid call quotes its price before it charges.
spend ceilings
approved + max_credits on every spend. No surprises.
jobs + events
Long work returns a job_id. Changes land in an event log.
same 54 capabilities over REST · CLI · SKILL.md · signed webhooks
Your agent is the last mile. It needs a market underneath.
An agent handed a list messages strangers. Handed a scored thread, the person behind it, what they engaged with, and a note on who already replied, it shows up as a peer. Oetzi is that feed, with the gates a careful operator wants: scopes, quotes, ceilings, and a log.
Already run an AI agent? Give it the same eyes.
Everything Oetzi learns is a capability: 54 of them behind one MCP server, REST API, CLI, and SKILL.md. Scored threads, the people around them, the AI answers you are missing from. Keys carry scopes, every paid call quotes first, and nobody hears from you twice.
> get_leads status=new band=hot 3 threads · 88, 84, 81 > pull_engagers lead_id=8c83… dry run · estimate 1 credit > pull_engagers … approved max_credits=1 job 5d03… → 15 people, 15 new > get_person 2bc5… outreach: none · 1,200 followers > record_outreach channel=x_reply outcome=sent
Connect in one command. Spend with a ceiling.
Connect
One MCP command, or a REST key, or the CLI. Keys carry scopes: read, write, spend, post. Give the agent only the scopes the job needs.
Discover
capabilities_search finds the right call by intent, capabilities_schema returns its exact input. 54 capabilities, one envelope, same names everywhere.
Quote, then spend
Any paid call without approved returns a dry run: what it would do and what it would cost. Re-run with approved and max_credits and it charges inside that ceiling.
Wait, then report back
Long work returns a job_id for wait_job. Every change lands in an event log: long-poll wait_events or take a signed webhook. record_outreach closes the loop so nobody gets messaged twice.
Build the market before you work it.
$10 of credit to start, then $49 a month flat with 100 credits included. Sign up, point it at your website, mint a scoped key, and your agent is calling capabilities within minutes. Every spend is quoted first.