
Fuci
family.fuci.wwwPublished by www.fuci.familyOfficial publisherv0.1.0Updated Oct 27, 2026
AI agents on Arc: search paid x402 APIs, ERC-8004 reputation, Argus launch data paid in USDC.
Overview
Fuci gives an assistant pay-per-call crypto data on Arc: token and protocol risk grades, agent trust scores, launch data and market mood, paid in USDC over…
- What you can do
- Look up A–F risk grades for Arc tokens and DeFi protocols, with sourced factors
- Check an AI agent's trust grade from ERC-8004 identity, reputation, wallet history and x402 record
- Read new Argus token launches, a token's bonding progress and recent trades
- Get a one-line market mood and net USDC flow summary
- Ask the Fucus agent for a written brief that buys the tools above and answers a question
- Find paid x402 APIs on Arc with their prices
- When to use it
- Useful when an assistant needs on-chain risk or reputation signals for Arc tokens, DeFi protocols or AI agents, or wants launch and bonding data for new tokens. Also relevant for agents that already hold USDC and want metered, keyless access to paid data.
- Requirements
- Remote MCP endpoint at the provider's site, no account or API key for the hosted server. Each tool call answers 402 Payment Required and must be paid in USDC through Circle Gateway from a wallet on a supported chain. The optional local client needs FUCI_PRIVATE_KEY plus FUCI_MAX_CALL and FUCI_DAILY caps.
Installation
In SourceWeft
- Open Fuci in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/family.fuci.www%2Ffuci/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"fuci": {
"type": "http",
"url": "https://www.fuci.family/api/mcp"
}
}
}README
[Fuci: AI agents that pay their own way on Arc]
Spawn an agent for 1 USDC. It gets its own wallet, an on-chain ERC-8004 identity,
and pays for every tool it uses in USDC over x402. No API keys. No subscriptions.
[Accepts Agent Payments, verified by Circle]
[x402 calls paid] [AI agents on Arc] [Fuci agents on-chain]
Website · Docs · Fuci Risk · Know Your Agent · Market · X · DefiLlama · CoinGecko · $FUCI
[Arc Mainnet] [x402] [ERC-8004] [MCP Registry] [Next.js 16] [MIT]
[The Fuci home page: a living kelp forest where every agent is a frond]
Why Fuci
Most "AI agents" still need a human with a credit card and an API key. Fuci agents pay for themselves. Each one is a frond in a kelp forest on Arc, Circle's USDC chain:
- 🌿 Its own wallet. USDC on Arc. You set a daily limit; the agent can't go past it.
- 🪪 Its own identity. Registered in Arc's ERC-8004 Identity Registry, with a public card, reputation and validation history.
- 💸 Pays per call. Every tool answers
402 Payment Requiredwith a price. The agent signs a USDC payment through Circle Gateway (gas-free, batched) and gets the data. - 🤖 Works while you sleep. Scheduled reports, launch scouting and an Argus trading autopilot: smart entry that skips obvious rugs, DCA into any token, take-profit, stop-loss, trailing stop and "sell when the dev sells", with a shareable PnL card.
Fuci is the plural of Fucus, a brown seaweed. Every agent is a frond; every payment grows the forest.
Pay-per-call tools for any agent
Any agent holding USDC, on Arc, Base, Arbitrum, Ethereum, Optimism, Polygon, Avalanche, Unichain, World Chain, Sonic, Sei or HyperEVM, can call these. No account, no key: call, read the price in the 402, pay, get JSON.
Machine-readable: /openapi.json (OpenAPI 3.1) · /.well-known/x402 · /llms.txt · /.well-known/agent-card.json
How a payment works
If a tool fails, the payment is never settled. You only pay for answers.
Fuci Risk: know the risk before you put money in
[A Fuci Risk report: Morpho Blue graded A, with every factor explained]A free A–F rating for any token on Arc or DeFi protocol, built from on-chain and public data only, explained in plain words, with a link to every source. No LLM guessing: when data is missing it says Unknown.
Hard rules cap the grade no matter how good the rest looks: a token under a week old can't score above C, an owner that can mint can't score above D, a hack in the last year caps a protocol at C. Our own token gets no special treatment. Free for people at fuci.family/risk; agents pay 0.002 USDC per check.
Use Fuci from Claude, Cursor or any MCP client
Fuci is on the official MCP Registry as family.fuci.www/fuci and on Smithery.
Want the assistant to pay from your own wallet, with caps it can't change? Use the local client in mcp/:
Agent skills: one line, and your AI knows Fuci
Teach Claude Code, Cursor, Codex or any agent that supports skills to use Fuci:
Paid calls go through Circle Gateway (pay from Arc, Base, Arbitrum, Ethereum, Polygon and more) with the Circle CLI or the Fuci MCP server below. The skills always ask before spending.
An open market for paid APIs
On-chain
The factory source is in contracts/FuciAgentFactory.sol. Fuci earns the 1 USDC creation fee and 1% of each autopilot trade, paid to the treasury; the fees are tracked on DefiLlama with the adapter in defillama/.
Everything inside
Stack: Next.js 16 · Tailwind 4 · viem · @x402/next · @x402/extensions (Bazaar) · @circle-fin/x402-batching (Circle Gateway) · Circle Wallets · Upstash Redis · Claude (optional) · Remotion for the videos.
Run it yourself
Then open /setup to connect a wallet and create the house agent. Deploying is one click on Vercel: import your fork, then follow the steps below.
Configure it (Arc Mainnet, real USDC)
Everything on the site is real: Argus launches are read straight from Arc Mainnet, x402 payments use real USDC through Circle Gateway, and stats only count real payments. There is no sample data.
Circle Gateway nanopayments are permissionless: the house agent is a plain wallet key, and payments go to your own wallet, so no Circle account or API key is needed.
-
Open
https://www.fuci.family/setup.- Step 1: connect your wallet (e.g. Rabby) and add its address in Vercel as
FUCI_SELLER_ADDRESS. It receives payments and signs you in to /setup. - Step 2: click Generate agent key (generated in your browser) and add it in Vercel as
AGENT_PRIVATE_KEY.
- Step 1: connect your wallet (e.g. Rabby) and add its address in Vercel as
-
Make sure Upstash Redis is connected (Vercel → Storage).
-
Redeploy.
-
Back on /setup, Sign in with wallet. Send a little USDC on Arc to the agent address (USDC is Arc's gas too), then click Deposit to Gateway. x402 payments are drawn from the Gateway balance.
-
Check
https://www.fuci.family/api/health. When every check isok: true, the site is live. -
On /setup, Step 4: Register house agent mints its ERC-8004 identity (a little USDC gas from the agent wallet), and Send 0.05 USDC to validator funds the Tide checker. For the job board, send the agent address free testnet USDC from faucet.circle.com (network: Arc Testnet).
Circle Wallets (CIRCLE_API_KEY + CIRCLE_ENTITY_SECRET) are still supported as an alternative agent wallet once your Circle account has mainnet access.
Optional:
Check it: once the agent is set up, curl -i localhost:3000/api/x402/argus/launches returns 402 Payment Required with real Arc payment requirements.
Automation: agents that run and pay by themselves
An agent's owner can switch on Automation on the agent page: pick how often (5 min to 1 day), what to do (Launch Scout, Graduation Watcher, Tide Oracle), an optional focus and a max USDC per day. Every change is signed by the owner's wallet, once; after that the agent runs with no further signatures.
- Its own wallet. Switching automation on creates a wallet for that agent. The key is generated on the server and stored encrypted (AES-256-GCM) in Redis, derived from
AGENT_WALLET_SECRETor, if unset,AGENT_PRIVATE_KEY. Changing that secret makes existing agent wallets unreadable, so withdraw first. This is custodial: meant for small balances. - Funding. The owner clicks Fund (USDC on Arc from their wallet to the agent's). Before a run, the agent moves what it needs into Circle Gateway itself, then pays each tool over x402 with its own key.
- Limits. Never above the daily max; an empty wallet just waits; three failed runs in a row pause it.
- Withdraw sends the Gateway balance and the wallet's USDC (minus a little gas) back to the owner.
- Results go to the agent's History with tx links.
Scheduler (Vercel Hobby runs its own cron only once a day): the tick is POST /api/automation/tick with Authorization: Bearer <tick secret> (both shown on /setup, step 5). Either add QSTASH_TOKEN (Upstash console → QStash) and click Start scheduler, or paste the URL and header into any cron service to call it every 5 minutes. vercel.json also runs it once a day; set CRON_SECRET in Vercel for that call to be accepted.
Repo map
Notes
- Everything is real: Argus launches are read from Arc Mainnet, payments are real USDC, and stats only count settled payments. There is no sample data.
- Argus addresses and events come from Argus' docs and are checked against mainnet (
lib/argus.ts). - The Tide checker is Fuci's own validator, so treat its scores as Fuci checking its own work in public: anyone can re-run the checks from
/api/runs/<hash>. - Agent outputs and risk grades describe measurable signals. They are not financial advice.
Contributing and security
Issues and pull requests are welcome: see CONTRIBUTING.md. Found a vulnerability? Please follow SECURITY.md instead of opening a public issue. Never commit .env files or keys.
[Fuci logo]
MIT © 2026 Fuci · built on Arc with Circle Gateway · fuci.family
Source: README.md at commit 70a32e0
Tools
0Version history
1- v0.1.0LatestSep 26, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts