Cowrie Research

byte-federal-primary-sources-2026-05-02

3 min read

Byte Federal primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current sources of truth were Byte Federal’s official site, API landing page, ByteConnect pages, and ByteMCP documentation.
  • The decisive signal in this pass was that Byte Federal exposes a broader operating stack—merchant payments, mobile-first auth, and MCP-native ATM discovery—rather than only a Bitcoin ATM map.

Primary-source snapshots

1) API platform overview

  • URL: https://www.bytefederal.com/apis
  • Key excerpt:
    • The API landing page groups the company’s developer surface into ByteAuth, ByteConnect, and ByteMCP.
    • It advertises enterprise-grade authentication, merchant payments, and AI-native ATM discovery in one stack.
    • It also markets 99.9% uptime, sub-100ms responses, and 1,400+ ATM locations.

2) ByteConnect POS / online payments

  • URL: https://www.bytefederal.com/byteconnect-crypto-point-of-sale
  • Key excerpt:
    • ByteConnect is presented as both point-of-sale and online payments infrastructure.
    • The page says ByteConnect supports all wallets, highlights ByteVault for faster transactions, and includes an administrative dashboard for sales, transaction data, and realtime charts.
    • It also foregrounds API integration and a web-based online-payments mode with a 1.50% transaction fee.

3) Merchant account setup

  • URL: https://www.bytefederal.com/byteconnect-crypto-point-of-sale/api/getting-started/account/
  • Key excerpt:
    • The merchant docs say setup begins in the ByteVault app and continues in WebWallet, where the merchant finishes business registration and configures backend features.
    • The docs explicitly say API access can be enabled from the merchant backend and that generated credentials are used for token-based authentication.
    • This is a strong signal that ByteConnect is a programmable merchant backend, not just a fixed POS screen.

4) ByteMCP introduction

  • URL: https://mcp-docs.bytefederal.com/getting-started/introduction/
  • Key excerpt:
    • ByteMCP is described as an MCP server that helps AI assistants find Byte Federal Bitcoin ATMs across the United States.
    • The docs list four tools: find_nearest_bitcoin_atm, get_atm_details, check_atm_status, and list_atms_by_city.
    • The docs emphasize live locations, timezone-aware open/closed status, distance sorting, and local or remote deployment.

5) ByteMCP tools overview

  • URL: https://mcp-docs.bytefederal.com/tools/overview/
  • Key excerpt:
    • The tools overview explains the natural-language-to-tool-call mapping for ATM discovery queries.
    • It shows location parsing across addresses, city/state strings, ZIP codes, and coordinates, and it says tools return structured data with counts and search-area metadata.
    • This is useful evidence that ByteMCP is not merely a static directory page but a reusable machine-facing location service.

6) ByteMCP API reference

  • URL: https://mcp-docs.bytefederal.com/integration/api-reference/
  • Key excerpt:
    • The API reference documents /health, /.well-known/mcp-server, /sse, and /mcp endpoints.
    • It shows JSON-RPC tools/call requests, enumerates the ATM tools, and publishes explicit rate limits for SSE and MCP requests.
    • The presence of a .well-known manifest plus transport endpoints makes ByteMCP look like a deliberate machine-readable access layer on top of the ATM network.

Working conclusion

Byte Federal is best cataloged as Bitcoin access and merchant-operations infrastructure rather than as only a Bitcoin ATM operator. The combined primary-source evidence shows a company operating several connected layers: consumer ATM access, wallet/app authentication, merchant POS and online payments, and MCP-native ATM discovery for AI assistants and other machine clients.

Graph View