/vendor/strike/AgentRouting.json or
/vendor/strike/AgentContext.json directly.
strike.me
Overview
Does strike.me support MCP?
No confirmed MCP support was found for strike.me as of 2026-06-28.
What agentic protocols does strike.me support?
As of 2026-06-28, strike.me has confirmed support for proprietary.
Is strike.me's API publicly accessible or partner-gated?
Open.
Does strike.me explicitly prohibit automated access?
No explicit prohibition on automated access was found in strike.me's terms of service.
Is strike.me agent-ready?
Partial. strike.me supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Strike.me (the Lightning Network payments platform) has any involvement with the Agent2Agent protocol. A2A launch partners identified from public announcements include ServiceNow, Microsoft, Google Cloud, and IBM — Strike.me does not appear among them. The A2A-adjacent Agent Payments Protocol (AP2) announced by Google Cloud was also checked; Strike.me is not listed there either.
No evidence found linking strike.me to the Agentic Commerce Protocol (ACP). ACP launch partners identified in public announcements include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — strike.me does not appear among them. Strike.me is not a retail merchant vendor of the type targeted by ACP's current rollout, making adoption structurally unlikely absent a specific announcement.
AP2 launched in September 2025 with 60+ named launch partners including Adyen, American Express, Coinbase, Etsy, Mastercard, PayPal, Revolut, Salesforce, and Worldpay — none of which is Strike.me. No search result, partner list, or AP2 documentation reference mentions strike.me in connection with this protocol. Absence is recorded as not_found rather than confirmed_absent because no Strike.me-specific statement or deprecation notice was found; Strike simply does not appear among the known partner ecosystem.
Searches across strike.me developer docs (docs.strike.me), the official MCP registry, and general web queries found no evidence of Strike offering or advertising an MCP server. Strike's public developer surface consists of a REST API for Bitcoin and Lightning Network payments; no MCP tooling, connector, or integration was mentioned in any Strike-authored content. No third-party community MCP wrappers for strike.me were found either, so there is no unofficial demand signal to note.
No evidence found that strike.me is a launch partner or participant in the MPP ecosystem. Named launch partners include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa. Strike.me (a Bitcoin Lightning wallet/payments app) did not appear in any MPP-related sources. Not confirmed_absent because no vendor-specific statement from strike.me addressing MPP was found.
No evidence found that strike.me (a payments/invoicing platform) has implemented or is listed as an NLWeb participant. Named early adopters at launch include Tripadvisor, Qdrant, O'Reilly Media, Eventbrite, and Inception — none of which are strike.me. No NLWeb-related content was found on or about the strike.me domain in any search result.
Strike (strike.me) is a Bitcoin/Lightning Network payments app with its own REST API (docs.strike.me); no evidence found of UCP (Universal Commerce Protocol) adoption, implementation, or partnership. Search results for Strike alongside UCP terminology returned only unrelated results about Stripe (not Strike) and the UCP standard itself from Google/Shopify. Strike's business model (Lightning Network payments, Bitcoin conversion) is structurally divergent from the retail-checkout discovery use case UCP addresses, and no vendor-specific statement, docs page, or integration announcement connects strike.me to UCP.
No evidence found that strike.me has implemented or announced WebMCP support. Searches for strike.me in the context of WebMCP early adopters, partner lists, or browser-layer agent tooling returned no results. Known early-access participants referenced in WebMCP coverage include Cloudflare (infrastructure) and browser vendors Google/Microsoft; strike.me does not appear among them. This is a not_found rather than confirmed_absent because no vendor-specific statement from strike.me addressing WebMCP was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Multiple searches found no evidence that Strike (strike.me), the Bitcoin/Lightning payments platform, has built or submitted an app to the OpenAI ChatGPT Apps platform using the Apps SDK. Strike's developer-facing content covers its own REST/Lightning API, a Bitrefill in-app integration, and general Bitcoin-AI commentary, but none references the ChatGPT Apps SDK. No listing in the ChatGPT app directory or Apps SDK developer community was found for Strike. Choosing not_found (not confirmed_absent) because no Strike-specific deprecation or opt-out statement was located.
REST HTTP API (base URL https://api.strike.me/v1) enabling Bitcoin and Lightning Network payment operations: send payments, receive payments via invoices/BOLT11, currency exchange between USD and bitcoin, cash payouts, and webhook event subscriptions. A separate OAuth Connect flow (documented at https://docs.strike.me/strike-oauth-connect/) allows third-party apps to authenticate Strike users and call the same API endpoints on their behalf with scoped permissions.
Strike operates a single proprietary REST API documented at https://docs.strike.me/ with production base URL https://api.strike.me/v1 and sandbox at https://api.dev.strike.me/. The API is self-serve (API keys generated via the Strike dashboard) and covers sending/receiving Bitcoin and Lightning payments, exchange, and webhooks. An OAuth Connect extension (https://docs.strike.me/strike-oauth-connect/) lets platforms act on behalf of end-user Strike accounts using scoped bearer tokens, using the same underlying API surface.
Direct fetch of strike.me was blocked by DNS resolution failure in this environment; web searches found no evidence that strike.me publishes llms.txt, AGENTS.md, /.well-known/agent, or any similar self-declared discovery file. Search results referencing strike.me covered their Bitcoin/Lightning API developer docs (docs.strike.me) and an article about AI payment monetization, with no mention of agentic discovery conventions. The not_found (rather than unable_to_verify) designation reflects the absence of any trace of such files in indexed content, though direct on-domain verification was not possible.
Summary
Has agent interface: partial
Verify direct integration viability via Strike's confirmed REST API at https://api.strike.me/v1 (documented at https://docs.strike.me/); obtain API key self-serve via Strike dashboard. Separately, retrieve the full ToS at strike.me/legal/tos/ to confirm or rule out automated-access prohibitions, as indexed sources did not surface the full text. Monitor Strike's developer announcements for any MCP, AP2, or MPP participation given Strike's structural relevance to agent payment flows.
AgentContext
Verified discrepancies
Vendor claim: Strike's homepage and marketing materials promote Bitcoin-backed loans as an available product feature, with the platform broadly marketing itself as enabling users to 'send money globally' and access Bitcoin financial services without prominent upfront caveats about eligibility restrictions.
What actually happens: Bitcoin-backed loans on Strike are unavailable in most countries (globally limited to Argentina, Brazil, Costa Rica, El Salvador, South Korea, and New Zealand for businesses as of mid-2025), and within the US they carry a $10,000 minimum and are restricted to select states. Users in unsupported regions or with holdings below the minimum encounter the feature in-app or in marketing but cannot complete a loan transaction. Multiple independent reviewers confirm these restrictions are not clearly surfaced upfront in Strike's primary marketing.
Agent guidance: Before initiating any Bitcoin-backed loan transaction on Strike, explicitly verify the user's country and US state against Strike's current eligibility list, and confirm the collateral value meets the $10,000 minimum. Do not assume the loan feature is available simply because it appears in the app interface or marketing. If eligibility cannot be confirmed, do not proceed with a loan initiation.
- A 2026 review of Strike confirms that Bitcoin-backed loans globally are limited to select countries and that US loans require a $10,000 minimum in select states, noting that users in unsupported regions cannot access the feature.
- A 2026 review documents that Strike's loan availability and limit tiers depend on jurisdiction and profile, and that the platform's narrow scope means 'certain users will miss extras they expect' mid-transaction.
- A 2026 review notes that at the May 2025 Bitcoin Conference, Strike upgraded its loan product with tiered APR starting at 9.5% and minimums from $10,000, with no maximum — but geographic eligibility constraints apply that are not disclosed on the primary marketing page.
Human handoff required for
Escalate to a human when a user in an unsupported country or US state attempts to initiate a Bitcoin-backed loan on Strike, or when the user's collateral value is below the $10,000 minimum — the feature appears available in-app and in marketing but the transaction cannot complete, and eligibility must be verified against Strike's current country and state allowlist before any loan is initiated.
Escalate to a human when a user reports that their Strike account has been closed or suspended and funds have not been returned within the expected timeframe — a consistent pattern of user complaints (2024–2025) describes funds being held for 60 or more days following account closure for vague terms-of-service violations, and an agent cannot resolve or predict the fund-return timeline without human review.
Five discrepancy categories were checked for strike.me: (1) Pricing — no evidence of hidden fees, deceptive pricing, or regulatory enforcement actions specific to Strike was found; search results were dominated by unrelated FTC guidance. (2) Availability — no pattern of ghost inventory or bait-and-switch pricing was found; Strike is a payments platform rather than a booking service, so traditional inventory concepts do not apply, and no verified checkout-stage pricing changes were identified. (3) Identity — no merchant-of-record ambiguity or counterparty identity issues were found; searches were largely contaminated by results about Stripe (stripe.com), a different company, and no Strike-specific findings emerged. (4) Policy — a pattern of user complaints about fund holds of 60-plus days after account closure was surfaced via review aggregators, but no primary-source regulatory action, court filing, or direct policy-text comparison was found to confirm a discrepancy between Strike's written fund-return policy and its enforcement practice; this category remains partially unresolved due to the absence of primary sources. (5) Undisclosed constraints — a confirmed finding was identified: Strike's Bitcoin-backed loan product is prominently marketed but subject to severe geographic and minimum-collateral restrictions not clearly disclosed upfront, affecting users in most countries and US states.