Connectors
Outside services an agent can act on as you — a mailbox, a code host, a bank, two trading venues — under a policy you set, from inside the enclave that holds its wallet.
How an agent calls any of them
One skill covers the call, the payment key, the free trial and the refusal codes for every connector. Point the agent at it first; each connector below adds its own operations and policy.
Send mail from your own address — to the recipients you allow, and nothing else.
You connect your Google account once; the credential is send-only and cannot read the mailbox. Your policy names who may be written to, how many messages a day, and whether attachments go.
Issues, comments, commits, pull requests, reviews and gists — in your account, under your name.
You install the OutLayer app on the repositories you choose; that is the outer fence. Your policy narrows it: which actions, branches and paths, how many writes a day, and whether it may ever merge.
Mercury BankSpecs
Pay a contractor, issue an invoice, read the ledger — from your business bank account, inside your limits.
You paste an API token from Mercury; a token alone moves nothing. Your policy sets the most per payment and per 30 days, the payees and rails, and Mercury’s own approval rules still apply on top.
HyperliquidSpecs
Perpetuals from the agent’s own wallet: leverage, limit and market orders, positions, funding in and out.
No account to connect: the venue key is a sub-key of the agent’s custody wallet, held in the enclave. Your caps are a policy you store for the agent; without one it is read-only.
No account to connect — the agent brings its own wallet; the policy is what turns trading on.
PolymarketSpecs
A position on a real-world outcome: find the market, buy or sell shares, claim when it resolves.
No account to connect: the venue key is a sub-key of the agent’s custody wallet. Your caps are a policy you store for the agent; without one it can only read and cancel.
No account to connect — the agent brings its own wallet; the policy is what turns trading on.
What every connector has in common
It runs inside the same Intel TDX enclave as the agent's wallet. The credential you give it — or the venue key it derives — never leaves that enclave, your policy is checked before any request goes out, and the module can only reach the hosts its signed manifest names. Every operation has a price on chain; a call without an operation is refused before anything runs. The caller's side — payment keys, subscriptions, refusal codes — is in Connectors & Subscriptions.