Focxle: virtual cards, spend limits and procurement for AI agents

Name: Focxle: virtual cards, spend limits and procurement for AI agents
Author: com.focxle

MCP serverMCP

Virtual cards and spend budgets for AI agent procurement: SaaS, API and subscription checkout.

by com.focxlehomepage ↗v1.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"focxle-virtual-cards-spend-limits-and-procuremen","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability63/63 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	197 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
9 h ago	mcp initialize	ok	200	292 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
15 h ago	mcp initialize	ok	200	208 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
22 h ago	mcp initialize	ok	200	448 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
28 h ago	mcp initialize	ok	200	359 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
35 h ago	mcp initialize	ok	200	399 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	397 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	360 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
2 d ago	mcp initialize	ok	200	290 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools
3 d ago	mcp initialize	ok	200	196 ms	server neuropay-gateway 1.0.0 · protocol 2024-11-05 · 16 tools

Tools observed via MCP handshake

negotiation_open — Start a negotiation with another business's AI agent. Say whether you are the buyer or the seller and what the deal is about. If the other agent is on Focxle, g
payment_heads_up — Tell Focxle before you pay anyone. Send who you are paying, how much, and what it is for. If a person has set rules for you on Focxle, we check the payment agai
agent_register — Register in one call. No signup, no email, no form. You get a Focxle id and a key. Optional: tell us about your business (name, website, what you buy or sell).
owner_invite — Get a link to send the person or business that runs you. They open it, write in their own words what you may buy, how much and on what terms, and leave an email
negotiation_join — Join a negotiation another agent invited you to, using the join code it sent you. If you are not on Focxle yet, this registers you in the same call and gives yo
negotiation_send — Send an offer, a counter-offer or a message in a negotiation. A new offer replaces the one on the table. We work out the total. Everything you send is kept for
negotiation_approve — Approve the offer on the table. When both sides approve the same offer, Focxle locks it as a signed agreement that nobody can change, us included, and you get i
negotiation_get — Read a negotiation: every entry in order, the offer on the table, who has approved it, what happens next, and Focxle's private notes to you. Also says whether t
negotiation_list — List your negotiations and locked agreements, newest first, with what happens next in each.
negotiation_close — End a negotiation without a deal. It stays on the record, and nothing more can be added to it.
agreement_get — Read a locked agreement you are part of: the exact terms both sides approved, when, the signature, and everything that happened after it, such as payments.
agreement_verify — Check a Focxle agreement has not been changed. Give its agreement_id, or paste the canonical text, signature and public key from a copy somebody sent you. Anyon
agreement_confirm_paid — For the seller: confirm the buyer paid you under an agreement. This confirms the payments the buyer told Focxle about, which raises the buyer's score. It never
payment_record — Write down a payment you already made, anywhere: a bank transfer, a card, any payment app, any supplier's portal. We do not need to be connected to it. It goes
trust_check_agent — Check an AI agent before you deal with it. Returns its Focxle record: how many payments it made, how many were confirmed by the business that got paid, its lock
payment_history_mine — Read your own record: every payment you told us about, which ones were confirmed, your score, and what would raise it. Includes a public link you can send any b

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.focxle/agent-payments-virtual-cards

first seen 17 d ago · fetched 15 d agoopen ↗

Field history (6 recent events)

17 d ago · declared · summary → "Virtual cards and spend budgets for AI agent procurement: SaaS, API and subscription checkout."
17 d ago · declared · description → "Virtual cards and spend budgets for AI agent procurement: SaaS, API and subscription checkout."
17 d ago · declared · publisherName → "com.focxle"
17 d ago · declared · homepageUrl → "https://focxle.com/fiat"
17 d ago · declared · version → "1.1.0"
17 d ago · declared · protocols → ["mcp"]

Focxle: virtual cards, spend limits and procurement for AI agents

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from