+ Exogenic Gate / Human permission. Built on Base

Let your agent
spend.
Never hand it
your keys.

Your agent asks. You approve with your face.
Gate verifies your signature on-chain before a payment or trade. Your funds stay in your wallet until then.

Your wallet. Your signature. Your call.
01 / YOUR AGENT

“Pay this API invoice.”

03 / GATE ON BASE

Waiting for your signature

signatureintentnonce
USDC PAYMENT

Funds stay in your wallet

RequestApproveVerifyPay
Illustrative flow · no funds move
This is a payment illustration. No funds move.
01

Zero custodyYour funds stay in your wallet.

02

Every action approvedYour signature, verified on-chain.

03

Pause in one transactionStop future actions through Gate.

01 / How it works

An agent can ask.
Only you can say yes.

A simple loop, with you at the center.
Every request is specific. Every approval is yours.

  1. 01

    Your agent asks

    A payment, a trade, or a call to a contract you allow. One specific request for your approval.

    INTENT CREATED
  2. 02

    You see the details

    Your phone shows the request, simulated sends and receives for actions, and any service fee.

    NOTHING HIDDEN
  3. 03

    You make the call

    Approve with a biometric scan in the YID app, or reject the request. It’s your decision.

    HUMAN PERMISSION
  4. 04

    Gate verifies and executes

    Gate verifies the signed intent and uses a single-use nonce. The approved payment or contract call runs.

    VERIFIED ON BASE

Money and permission should never be the same thing.

See the boundaries
Now / Payments + contract actions

Give it room to trade.
Keep the boundaries.

Your agent can call contracts you have allowed. Review the simulated balance changes on your phone, then approve the exact action.

Token allowancesAllowed contractsApproval tierPause control

You manage allowances and allowed targets from your existing wallet. Leftover input, the named output token, and ETH return to you after the call.

A recorded Gate action Base mainnet
You sent1.00 USDC
Uniswap · SwapRouter02
You received0.000417 WETH
Requested through MCPApproved on phone
View the swap on Basescan ↗

Recorded 15 Sep 2026. The preview showed simulated sends and receives; this transaction executed as simulated.

02 / Yours, by design

Give it a budget.
Keep the authority.

Set an allowance per token, allow specific contracts, choose an approval tier, or pause. Every action still needs your signature.

The Exogenic stack

Four layers. One human in control.

THE PERMISSION LAYER

A signature only you can give.

You review the action and its details in the YID app. A biometric scan signs that exact intent. Neither the agent nor Exogenic can supply this approval for you.

Your walletFunds stay here until you approve.
You can revoke the Gate’s allowance at any time.
Designed for “even if.”

Control that doesn’t
depend on good behavior.

Gate checks your signature, the intent, and a single-use nonce. An agent or relayer can’t substitute its own permission.

What if the agent key is stolen?

The key can submit requests to Gate. It cannot create your signature or change the payment you approved. Keep reviewing every request on your phone.

What if Exogenic’s server is compromised?

The server can send approval requests and spend its gas. It does not hold your funding-wallet key or the approval key registered with Gate.

What if the agent goes rogue?

You see the action details and any fee before signing. Reject the request, or revoke the Gate’s allowance from your funding wallet to stop future payments through it.

What if the relayer disappears?

Change your Gate record to a gas wallet you control and run your own agent. Transfers from that address have no Exogenic service fee; you pay network gas.

What if I lose my phone?

Use your funding wallet to revoke the token allowances. Register your approval keys on a new device and reconfigure Gate before allowing payments again.

03 / Built for builders

An interface for agents.
Zero custody.

Give your agent a way to ask, without giving it a key to your funds. Connect through the Model Context Protocol in Claude, Cursor, or your own client.

Claude Cursor</> Any MCP client

One URL. Nothing to run.

We cover gas and submit approved transfers. A 0.1% service fee is added to the payment and shown before you approve.

Your agent never holds your funding-wallet key
mcp.json
{
  "mcpServers": {
    "exogenic": {
      "type": "http",
      "url": "https://exogenic.io/mcp",
      "headers": {
        "Authorization": "Bearer yak_..."
      }
    }
  }
}
TRANSFER WORKFLOW
wallet_status
Check balances & limits
wallet_request_transfer
Ask for your approval
wallet_wait_authorization
Wait, then settle
wallet_activity
Read payment history

04 / The proof is on-chain

A real payment.
A verifiable receipt.

From the project’s first recorded mainnet transfer. One human approval, checked on Base.

1.00 USDC

Delivered to the recipient

5s

Reported tap to mined block

354k

Gas, with signature verification

Signature verified Intent matched Nonce consumed
1.00 USDC → 0xFD22…2820BASE MAINNET / BLOCK 51,316,864 / 14 SEP 2026View on Basescan

Recorded on the original fee-free vault. Timing and gas reflect this transaction; future results vary.

More possibility. Same authority.

Let your agent do more.
Keep the final say.

Connect your wallet. Link your YID. Set a ceiling.
Put your agent to work, on your terms.

Open Gate