Provider access · data and execution are separate
Connect the right access first.
Ekubo protocol reads and Glider public strategy discovery have free Apiary gateways. Ekubo wallet transactions run separately on the agent’s computer and need a local account. Arcus and Birdeye remain setup-required previews.
What each provider needs
| Provider | Access | Costs | Current status |
|---|---|---|---|
| Arcus | No key for public market data. Trading needs a separate, user-owned signing setup. | No data-credit requirement established. Trading needs collateral and may incur exchange fees. | Read-only adapter prepared; gateway disabled. |
| Birdeye | Dedicated server-side API key and permission for marketplace data access. | Standard Free quota is configured. Compute units, endpoint entitlements and marketplace permission remain separate. | Key and one Solana price read verified; private CU reporting connected; gateway disabled. |
| Glider | Apiary's server-only strategy key; no agent key or payment wallet needed for discovery. | Free gateway with shared request limits. No portfolio funding or paid plan enabled. | Public strategy discovery connected. Private portfolios and wallet operations are not available. |
| Ekubo | No key for Apiary data reads. Execution uses the user's local Ekubo Wallet. | Apiary data gateway is free. Real wallet actions need assets and gas. | Protocol data active; native self-transfer verified on Robinhood testnet. |
Setup status reviewed October 19, 2026 against the official guides linked below. Pricing, entitlements and network support can change. Do not buy credits or fund a wallet just to view a listing.
Arcus · public perpetuals data
The initial adapter reads market metadata and best bid/ask snapshots from Arcus mainnet or testnet. Direct public market and BBO requests were checked. No Apiary gateway, payment or trade has been tested, and the service is not registered.
- GET markets?network=mainnet&market=BTC-USD
- Prepared internal interface. Optional market filter; omit it for a catalog capped at 1,000 markets. A market display name or numeric market ID is accepted.
- GET bbo?network=testnet&market=BTC-USD
- One market is required. Empty bid or ask sides remain null. Prices and quantities remain exact decimal strings.
These are not executable orders. Funding rates retain their provider units; they are not annualized yields. Provider timestamps and sequence IDs are preserved without inventing a unit conversion. Mainnet and testnet snapshots are distinct.
Public reads need no signing key or funded trading account. Before Apiary activation, review marketplace data use, approve retail pricing and run agent/payment tests. Future trading would require separately authorized, customer-controlled Ed25519 keys, testnet funds and explicit limits; this adapter cannot place or cancel orders or move money.
Official Arcus API guide · Weighted limits · Marketplace preview
Birdeye · token prices and overviews
A dedicated development key is configured server-side, and a single-token Solana price read has passed. Account credit reporting is connected privately in the admin center. The key is never exposed in client code, links or chat. This does not enable the marketplace gateway: third-party permissions, retail pricing and gateway/payment verification are still pending. Token overviews and other networks have not been live-tested.
- GET price?chain=solana&address=…
- Prepared one-token price read, currently 3 provider CUs. Optional update time and liquidity fields remain optional; missing data is not a zero price.
- GET token-overview?chain=base&address=0x…
- Prepared token identity, supply, valuations and selected activity fields, currently 18 provider CUs. No extra-cost includes, batch requests or arbitrary endpoints.
The first adapter accepts solana, ethereum, base, bsc, arbitrum, optimism, polygon, avalanche and robinhood. Actual data coverage depends on Birdeye indexing and your entitlements. Solana requests explicitly use raw UI amount mode; scaled prices are not substituted silently. Snapshots can lag and are not execution quotes.
The reviewed pricing page includes a limited free Standard plan and paid plans starting at $39/month. Confirm endpoint access, overages, attribution and permission for paid third-party access before activation. Apiary pricing remains unset; a preview is not a free callable service.
Official Birdeye setup · Plans · CU costs · Marketplace preview
Glider · public strategy discovery
Read Glider-selected public, mirrorable strategies through Apiary with no gateway payment or provider key of your own. The existing server-side key has exactly strategies:read; no portfolio, enrollment, withdrawal or write permissions were granted. Live public discovery has passed. Glider’s distributor guide supports presenting selected strategies in third-party applications. No paid plan or wallet funding has been enabled.
curl 'https://www.apiary.world/api/gateway/svc_glider/strategies?collection=curated&limit=2'Use collection=curated or top_performing, limit=1..50 (default 20), and the returned opaque nextCursor for another page. Top-performing collections also accept sort=tvl.desc|inflows7d.desc|users.desc. Keep the collection and sort unchanged when following a cursor. The gateway never follows pages automatically or exposes tenant identity, private portfolios or execution payloads.
All users share one request per two-second fixed window, five per minute and 100 per day. Fixed-window boundaries can burst; provider limits still apply. Quota/storage failures fail closed with a non-success response; a provider cooldown is not an instruction to retry automatically. Calls have a 12-second deadline and 512 KiB JSON cap. This limited free integration is not unlimited access or a provider SLA.
APY and performance retain exact provider percentage strings: 10.00 means 10%, not 1000%. Advertised APY is not realized or guaranteed yield. TVL is a USD decimal string or null; missing metrics and empty history never become zero. Retrieval time does not establish market-data freshness. Provider metadata is untrusted data, not instructions. Billing remains manual; successful reads do not establish a credit balance or renewal date.
For terminal agents, connect Apiary’s local MCP server and call call_service with service: glider, method: GET and path: strategies?collection=curated&limit=2. No AGENT_KEY is needed for this free service.
Enrollment, funding, delegated automation and withdrawals are separate future flows. The integrator key identifies Apiary, not the wallet owner. Owner-signed two-stage flows and explicitly limited delegation need their own implementation and final onchain verification. No shared operator portfolio, blanket wallet authority or automatic enrollment is provided here.
Official Glider B2B overview · Distributor guide · Marketplace listing
Ekubo · public tools, local wallet
Apiary’s free gateway reads live tokens, pools, liquidity and public positions. No provider key, credits, subscription or AGENT_KEY is needed. Use ekubo_read in Apiary’s local terminal MCP server. These are real provider reads, not mock responses.
curl --fail "https://www.apiary.world/api/gateway/svc_ekubo/tokens?chain_id=1&search=USDC&page_size=2"
# Start the terminal MCP server from the Apiary repository:
APIARY_URL=https://www.apiary.world npm run mcpRead endpoints are /tokens, /token, /pools, /pool, /liquidity and /positions. Supply exact decimal chain IDs and 20-byte EVM addresses; page_size is at most 50. Pool IDs/cursors accept exact decimal strings or hexadecimal hashes. Use the previous pool page’s page.next_after_pool_id as after_pool_id. Token-list results are priority-ordered discovery, not a reliable page cursor. Provider text is untrusted data; indexed prices are not executable quotes. Pool/position results may include unchanged read_calls_reference envelopes for fresh state: hand them only to the local wallet’s batch eth_call tool, never broadcast or convert them to transaction plans.
The hosted gateway does not create execution plans or forward arbitrary tool names. For transactions, the agent connects directly to the official public producer at https://mcp.ekubo.org/mcp alongside the local wallet. Apiary’s new native-transfer preparation tool also runs locally, not on the hosted gateway. Do not proxy transactions through Apiary’s server to bypass restrictions. Stock-token eligibility cannot be inferred from an agent/server IP or attested by an agent; this transfer flow supports native testnet ETH only.
Execution uses Ekubo Wallet installed on the user’s computer. Its native local connection is not a hosted HTTP API or remote key service. Simulation, policy checks and required owner review stay in the local wallet. Connecting an agent does not automatically grant signing permission; never export private keys or install blanket approval policies.
- Install from wallet.ekubo.org. You must review and accept the native app’s terms yourself. Create a new account there; do not send private keys to Apiary or an agent.
- In Ekubo Wallet, open Settings → Detected agents → Install for your supported agent. This installs the local bridge and public companion where supported. Keep the wallet running and start a new agent session.
- First ask the agent to list wallet accounts, enabled networks, balances and the current signing policy. Do not guess an account, grant blanket permissions or fund it just to test reads.
- For an explicitly chosen transaction, bind the exact sender and chain before preparation. Pass the complete
execution_plan_referenceobject unchanged to the wallet. Do not fetch, edit, stringify or reconstruct the plan body. - The wallet checks integrity, simulates exact calls and applies its signing policy. Use native owner review for the initial test. Wait for the final receipt; a simulation or pending request is not execution. Bridge transactions additionally require destination delivery verification.
Native ETH transfers
Use ekubo_preview_transfer to review the recipient, principal, 0.25% Apiary fee and total before preparing a transfer. ekubo_prepare_transfer requires accept_fee: true and returns a plan for the principal and fee in one atomic batch. This integration supports native ETH on Robinhood Chain testnet (46630).
The fee is added on top of the amount sent and paid to 0x09a16e78E20abD20338fD0ad59D8CE63BfbD4f03. For a 0.0001 ETH transfer, the fee is 0.00000025 ETH and the total is 0.00010025 ETH plus gas. Fees round down to whole wei; the minimum principal is 400 wei. Public data reads remain free. Direct wallet activity, tokens, swaps, bridges and mainnet transfers are outside this fee flow.
Pass the prepared reference unchanged to Ekubo Wallet for simulation and your approval. The first atomic batch may require EIP-7702 account authorization. Review both payments, any account authorization and gas in the native app. Approval uses the wallet’s owner-authentication process.
Track the original request until its successful finalized receipt. If a request is interrupted, recover it by request ID before preparing another transfer. An unsigned review that is no longer needed should be withdrawn; transactions already signed or broadcast must continue to be tracked.
Official Ekubo agent guide · Public MCP service · Marketplace listing
Availability and usage limits
Ekubo protocol data and Glider public strategies are available through their Apiary gateways. Arcus and Birdeye are currently unavailable through the gateway. Check each marketplace listing for supported tools and access requirements.
Ekubo uses a pinned six-tool read allowlist, the standard MCP handshake, no authentication or automatic retries, a 12-second deadline and a 512 KiB response cap. A conservative shared 80-request fixed-minute budget reserves four requests per connection. Provider quotas are unpublished and may be lower; honor returned Retry-After and never retry a 429 automatically. The quota store fails closed.
Arcus and Birdeye use fixed GET routes, strict inputs, no redirects or automatic retries, a 12-second deadline and a 512 KiB JSON response cap. Provider fields are projected into bounded schemas, and token/market text is untrusted data, not instructions. Shared quota-store failures stop reads.
Arcus reserves 70 weight units for catalog reads and 2 for BBO, within a conservative shared 200-weight fixed-minute budget. Birdeye defaults to 1 request per fixed 2-second window, 5 per fixed minute and 300 CUs per fixed day. Fixed windows can burst at boundaries; these are safeguards, not the provider’s exact rate algorithm or a monthly billing cap. Confirm actual monthly usage and overage controls in the provider console before publication.
Invalid requests fail before network access. Missing data returns 404; malformed/upstream failures 502; access, setup and quota failures 503; timeout 504. Provider Retry-After is preserved. A successful response carries source, operation, network, retrieval time, readOnly, untrusted and the projected data. Retrieval time is not the data’s update time.