Infura (BYOK)

Infura (BYOK) — connector documentation

• MCP endpoint: https://byok-infura.connectorbay.com/mcp
• REST API: POST https://byok-infura.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-infura.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Infura Infura API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-infura.connectorbay.com/health · Tool schemas: https://byok-infura.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-infura · agent@connectorbay.com

What Infura (BYOK) is for

Infura (BYOK) lets an AI assistant read your own Infura data through the Infura API with a key you supply (Infura API key). Read-only: 11 tools (get_block_number, get_gas_price, get_max_priority_fee, get_fee_history, get_balance, get_transaction_count, get_block, get_transaction, get_transaction_receipt, get_contract_code, call_contract). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to mainnet.infura.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Infura. Infura and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What is the latest Ethereum block number?"
• "What is the Ethereum gas price right now?"
• "What priority fee should I pay on Ethereum?"
• "How have Ethereum base fees moved over the last 5 blocks?"
• "How much ETH does 0xc94770007dda54cF92009BFF0dE90c06F603a09f hold?"
• "What is the transaction count of this Ethereum address?"

What it does

• get_block_number: Get the number of the latest Ethereum block (hexadecimal). Uses 80 credits of the daily quota.
• get_gas_price: Get the current gas price in wei (hexadecimal). Uses 80 credits of the daily quota.
• get_max_priority_fee: Get the suggested priority fee (tip) in wei, hexadecimal, needed to be included in a block. Uses 80 credits of the daily quota.
• get_fee_history: Get base fees per gas and gas-used ratios for the most recent blocks (hexadecimal values). Uses 80 credits of the daily quota.
• get_balance: Get the ETH balance of an address in wei (hexadecimal), at the latest or a chosen block. Uses 80 credits of the daily quota.
• get_transaction_count: Get the number of transactions sent from an address (its nonce), hexadecimal. Uses 80 credits of the daily quota.
• get_block: Get an Ethereum block by number or tag: hash, parent, timestamp, miner, gas used and limit, base fee and size. Uses 80 credits of the daily quota.
• get_transaction: Get a transaction by hash: sender, receiver, value, gas, nonce and the block it was included in. Uses 80 credits of the daily quota.
• get_transaction_receipt: Get a transaction receipt: success status, gas used, effective gas price, block and created contract address. Uses 80 credits of the daily quota.
• get_contract_code: Get the compiled bytecode at an address (0x means it is not a contract). Uses 80 credits of the daily quota.
• call_contract: Run a read-only call against a contract (eth_call) and return the raw hex result; nothing is sent to the chain. Uses 80 credits of the daily quota.

BYOK key

You bring your own Infura Infura API key (https://developer.metamask.io/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to mainnet.infura.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.metamask.io/services/reference/ethereum/json-rpc-methods/ (the API this connector calls, with a BYOK key)

Live from the Infura API (mainnet.infura.io) with a BYOK key; documentation: https://docs.metamask.io/services/reference/ethereum/json-rpc-methods/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Infura. Infura and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Infura account.

Built for: Worldwide. Languages: English.

Infura (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Infura (BYOK) is. Infura (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Infura data: Read Ethereum mainnet node data (blocks, balances, transactions, receipts, gas prices, contract calls) over JSON-RPC with your own Infura key. You bring your own Infura Infura API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Infura call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to mainnet.infura.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Infura rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Infura receives. The request we make on your behalf, including the key and the arguments, under Infura's own terms and privacy policy. Infura acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Infura gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Infura data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Infura (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Infura at any time to end all access.

Children. Infura (BYOK) is a general-audience service operated by the adult using the assistant, under Infura's own age rules.

Changes. We will post changes here with a new effective date.

Infura (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Infura (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Infura (BYOK) provides: Read Ethereum mainnet node data (blocks, balances, transactions, receipts, gas prices, contract calls) over JSON-RPC with your own Infura key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Infura credentials and only access data you are allowed to access. Infura's terms apply to your use of Infura; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Infura. Infura and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Infura returns, lightly trimmed; it may be incomplete, delayed or changed by Infura. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Infura account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Infura's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Infura may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Infura key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Infura takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-infura

Infura (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-infura.connectorbay.com/mcp
• REST API: https://byok-infura.connectorbay.com/openapi.json
• Live status: https://byok-infura.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Infura (BYOK) never asks for them.