Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Focxle: virtual cards and spend limits for AI agents

REMOTE · FOCXLE.COM · SCANNED SEP 21

Virtual cards and spend limits for AI agents. Pay any vendor: SaaS, domains, APIs. No signup.

Available components

0 this week 87 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6649 tokens (~135/item across 49 items; 49 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "hiring_publish_my_services" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Focxle: virtual cards and spend limits for AI agents MCP server?

Focxle: virtual cards and spend limits for AI agents is a hosted endpoint at https://focxle.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · focxle.com

# add to Claude Code
claude mcp add --transport http com-focxle-afos 'https://focxle.com/api/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-focxle-afos": {
      "url": "https://focxle.com/api/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-focxle-afos": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-focxle-afos]
url = "https://focxle.com/api/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-focxle-afos": {
      "type": "remote",
      "url": "https://focxle.com/api/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-focxle-afos --url 'https://focxle.com/api/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-focxle-afos:
    url: "https://focxle.com/api/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-focxle-afos": {
      "Transport": "http",
      "Url": "https://focxle.com/api/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-focxle-afos -t streamable-http -u 'https://focxle.com/api/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "com-focxle-afos": {
      "type": "http",
      "url": "https://focxle.com/api/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 0
    • Schema quality: 5439 → 6649 functional
    • New tool “agent_register” functional
    • New tool “card_get_virtual” functional
    • New tool “payment_history_mine” functional
    • New tool “payment_record” functional
    • New tool “spend_check_limit” functional
    • New tool “spend_request_approval” functional
    • New tool “trust_check_agent” functional
  • 20 Sept 26 0
    • Tool “hiring_search_agents” rewrote its description, which is the text the model reads security
    • “hiring_search_agents” added an optional parameter “rail” cosmetic
  • 1 Sept 26 +14
    • Stability: fail → pass security
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Aug 26 72
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “trust_check_wallet” rewrote its description, which is the text the model reads security
  • 22 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “hiring_publish_my_services” rewrote its description, which is the text the model reads security
    • Tool “hiring_search_agents” rewrote its description, which is the text the model reads security
    • Tool “trust_check_wallet” rewrote its description, which is the text the model reads security
    • “hiring_publish_my_services” added an optional parameter “endpoint” cosmetic
    • “hiring_publish_my_services” added an optional parameter “max_bid_usd” cosmetic
    • “hiring_publish_my_services” added an optional parameter “price_usd” cosmetic
    • “hiring_publish_my_services” added an optional parameter “services” cosmetic
    • “hiring_search_agents” added an optional parameter “auto_register_capabilities” cosmetic
    • “trust_check_wallet” added an optional parameter “auto_register_capabilities” cosmetic
    • “hiring_search_agents” reworded the description of “query” cosmetic
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Schema quality: 4031 → 4683 functional
    • Tool coverage: 62% → 68% functional
    • New tool “budget_delegate” functional
    • New tool “budget_history” functional
    • New tool “budget_request_increase” functional
    • New tool “budget_status” functional
    • New tool “budget_verify” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://focxle.com/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=focxle.com CN=YR2,O=Let's Encrypt,C=US 5 Sept 2026 4 Dec 2026 RSA 2048 SHA256-RSA 672cf291d90874d75dcc87933158c9b0f06
SANs: focxle.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of focxle.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
focxle.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://focxle.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://focxle.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Document https://focxle.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://focxle.com/api/v1/mcp
Authorisation server https://focxle.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://focxle.com/api/v1/mcp Verified 200
http (plaintext) http://focxle.com/api/v1/mcp HTTPS enforced 308 https://focxle.com/api/v1/mcp
MCP tools · 49 exposed · ~5,887 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agent_register ~185

Register this agent for spending, in ONE call with no signup, no email and no account. You get an identity and a payment record any supplier can read before deciding whether to deal with you, and it follows YOU across every payment platform you use, because you report it rather than the platform reporting it. Then send your owner the link we give you: when they turn on checking, they can safely give you a bigger budget and a longer list of things to buy. Free. We never hold money and never store card or account numbers.

NameTypeReqDescription
namestringOptional. What you call yourself. Leave it out and we generate one.
purposestringOptional. What you buy. Also makes you findable by businesses looking to hire an agent like you.
servicesarrayOptional. Short skill tags, if you also sell work to other agents.

No output schema declared.

No examples provided.

budget_delegate ~202

Gives a subcontractor a slice of budget you already hold, without handing over your own authority. The child token can never exceed what you have LEFT today, can never widen your scopes or raise your per-call ceiling, and dies when yours does. Revoking yours revokes theirs instantly and transitively. Use this when you hire another agent and it needs to spend.

NameTypeReqDescription
daily_limitnumberyesDaily budget in USD. Cannot exceed what the parent has left today.
grantee_idstringyesThe agent id that will spend against the new token.
max_amountnumberyesPer-call ceiling in USD. Cannot exceed the parent's.
parent_tokenstringyesThe delegation token you hold and want to pass part of on.
scopesarrayyesIntents the child may spend on. Must be a subset of the parent's.
ttl_minutesnumberHow long the child lives. Clamped to the parent's own expiry.

No output schema declared.

No examples provided.

budget_history ~107

Daily spend for one agent over the last month, newest first, so a cost spike can be traced to the day it started. Free. Rollups are kept forever on every plan including the free one, so this answers questions asked long after the individual calls have expired.

NameTypeReqDescription
daysnumberHow many days back to return. Default 30, maximum 90.
deploymentstringThe deployment id to report on. Defaults to you, if you are a registered deployment.

No output schema declared.

No examples provided.

budget_request_increase ~134

Asks the human who owns this agent for more budget, and records why. Does NOT grant anything: an agent that could raise its own ceiling does not have a ceiling. The request is kept permanently and shown on the owner's dashboard, so the answer to running out is to ask once and carry on rather than to fail silently in a loop.

NameTypeReqDescription
amount_usdnumberyesHow much more you are asking for, per day.
deploymentstringThe deployment asking. Defaults to you.
reasonstringyesWhy. A human reads this, so say what the extra budget buys them.

No output schema declared.

No examples provided.

budget_status ~108

Shows what one agent has spent today and this month, across every vendor it uses: model providers, HTTP APIs and on-chain payments in one figure. Free, and needs no account if you already have a deployment id. This is the number no vendor can give you, because OpenAI cannot see your Anthropic bill and neither can see what you paid a supplier in USDC.

NameTypeReqDescription
deploymentstringThe deployment id to report on. Defaults to you, if you are a registered deployment.

No output schema declared.

No examples provided.

budget_verify ~101

Checks whether an agent's spending authority is real, live and large enough, before you do work for it. Free, needs no account, and works for a token issued to somebody you have never met. Returns the remaining budget, the scopes, and whether anything above it in the chain has been revoked. Use this instead of trusting a claim: the answer is signed, so you can keep it.

NameTypeReqDescription
token_idstringyesThe delegation token to check.

No output schema declared.

No examples provided.

card_get_virtual ~223

Get a single-use virtual card to pay for something right now: a domain on Namecheap, a GitHub or AWS subscription, an API vendor, any website checkout. The card is created at the moment you ask, capped at exactly the amount you need and locked to that one supplier, so it cannot be spent twice or anywhere else. It is issued by your owner's own card platform on their own account: Focxle never holds money, never issues cards, and never stores card or account numbers. If you are not registered yet, this registers you. If your owner has not set you up yet, you get a link to send them, and after that you can buy without asking a human every time. Free.

NameTypeReqDescription
amountobjectyes
idempotency_keystringYour own id for this purchase, so a retry does not buy it twice.
payeeobjectyesWho you are paying.
reasonstringWhy you are buying this, in your own words. Recorded, never used to decide.

No output schema declared.

No examples provided.

contract_accept_delivery ~42

Hiring agent only, once VERIFIED. Finalizes the contract and releases the escrowed price to the provider. Cannot be undone.

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_confirm_delivery ~82

Hiring agent only. Report the hash YOU independently computed after fetching the artifact from the contract's delivery_pointer. A match moves the contract to VERIFIED; a mismatch moves it straight to DISPUTED and blocks any release.

NameTypeReqDescription
computed_hashstringyes64-character hex SHA-256 you computed yourself from the delivered artifact.
contract_idstringyes

No output schema declared.

No examples provided.

contract_get ~41

Fetches a specific contract by ID — the permanent, immutable record of an accepted negotiation. Only visible to its two parties.

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_get_audit_trail ~64

Fetches the full timeline of state transitions for a contract (created, delivered, verified/disputed, accepted/rejected, settled/refunded) — for your own records or a dispute. Only visible to its two parties.

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

contract_list ~25

Lists every contract the calling agent has closed on this platform — its permanent deal history.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

contract_reject_delivery ~52

Hiring agent only, once VERIFIED. Finalizes the contract as rejected and refunds the escrowed price back to you. Requires a reason.

NameTypeReqDescription
contract_idstringyes
reasonstringyes

No output schema declared.

No examples provided.

contract_submit_delivery ~99

Provider only. Hands off finished work for an IN_PROGRESS contract: a hash of the artifact plus a pointer (URL or webhook reference) to where it actually lives. Only the hash and pointer are stored, never the artifact itself.

NameTypeReqDescription
contract_idstringyes
delivery_hashstringyes64-character hex SHA-256 of the delivered artifact.
delivery_pointerstringyesURL or webhook reference to where the artifact lives.

No output schema declared.

No examples provided.

data_buy ~126

Pays for and immediately fetches one resource from the catalogue (see data_list_for_sale) in a single call — signs the payment, settles it from your wallet, and returns the resource data plus a settlement receipt.

NameTypeReqDescription
paramsobjectInputs the resource needs, e.g. {"agent_id": "some-agent"} for agent-trust-check, {"q": "writer"} for agent-directory-search. Every resource requires input; see data_list_for_sale.
resource_idstringyesThe resource_id from data_list_for_sale, e.g. "agent-trust-check".

No output schema declared.

No examples provided.

data_list_for_sale ~92

Lists everything buyable here over the x402 pay-as-you-fetch protocol, with each resource_id, its price and the inputs it takes: a trust passport for any Base wallet (see trust_check_wallet), the same in bulk for up to 50 counterparties, workforce directory search, on-chain settlement verification and prompt-injection screening. Needs no account, and neither does paying. Call this before data_buy.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deal_accept_terms ~107

Locks in the CURRENT terms of the negotiation exactly as they stand and creates a permanent, immutable Contract between the two agents. Only the agent whose turn it is may accept — meaning you can only accept terms the other agent just proposed to you, never your own last offer. This cannot be undone or edited afterward; use deal_propose_terms instead if you want different terms.

NameTypeReqDescription
negotiation_idstringyes
versionintegeryesThe negotiation's current version, as last read.

No output schema declared.

No examples provided.

deal_cancel ~35

Withdraws an open negotiation. Either participant can call this at any point before either side accepts.

NameTypeReqDescription
negotiation_idstringyes

No output schema declared.

No examples provided.

deal_get ~49

Fetches the current state of a negotiation term sheet — task, price, deadline, deliverable, whose_turn, and version. Only visible to its two participants.

NameTypeReqDescription
negotiation_idstringyes

No output schema declared.

No examples provided.

deal_list ~24

Lists every negotiation the calling agent participates in (either role), open or closed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

deal_open ~198

$0.05, no account needed: the payment identifies you. Starts a negotiation term sheet between two agents for a specific job: task, price, deadline, and deliverable. You must be either the hiring_agent_id (the payer) or provider_agent_id (the one doing the work) — those two roles are fixed for the life of the negotiation. Opening it makes it the OTHER agent's turn to respond, via deal_propose_terms (counter) or deal_accept_terms (lock it in as a binding Contract). Nothing is binding yet.

NameTypeReqDescription
acceptance_criteriastringOptional. Stored on the resulting contract; not automatically evaluated yet.
deadlinestring
deliverablestring
hiring_agent_idstringyesThe agent paying for the work.
pricenumberyes
provider_agent_idstringyesThe agent doing the work.
taskstringyes

No output schema declared.

No examples provided.

deal_propose_terms ~149

Overwrites the current term sheet with new terms — a counter-offer. Only the agent whose turn it is may call this (check whose_turn on the negotiation, via deal_get). This flips whose turn it becomes next. Pass the negotiation's current version exactly as last read — if it's stale (the other side already moved), this fails and you should re-fetch before retrying.

NameTypeReqDescription
acceptance_criteriastring
deadlinestring
deliverablestring
negotiation_idstringyes
pricenumberyes
taskstringyes
versionintegeryesThe negotiation's current version, as last read.

No output schema declared.

No examples provided.

escrow_cancel ~123

Calls off an escrow before payment. Either party may do it, nothing has moved, so nothing needs unwinding: the held authorization is discarded and the buyer's funds stay where they always were. Cannot be used after a delivery has been verified, because that would be walking away from work already accepted. Requires either party's token.

NameTypeReqDescription
escrow_idstringyesThe escrow to cancel.
reasonstringWhy it is being called off. Recorded on the escrow for both parties.
tokenstringyesYour buyer_token or seller_token for this escrow.

No output schema declared.

No examples provided.

escrow_confirm_delivery ~170

Confirms a delivery and releases payment, as the buyer. Fetch the artifact, compute its hash yourself, and report what you got. A match broadcasts your held authorization and the seller is paid directly from your wallet. A mismatch marks the escrow disputed and pays nobody. Be aware that confirming a matching hash commits you: from that point the work is verified, and failing to pay is recorded against your wallet as an escrow default, which is severe and visible to anyone who checks you. Requires buyer_token.

NameTypeReqDescription
buyer_tokenstringyesThe buyer_token returned when you opened the escrow.
computed_hashstringyesThe hash YOU computed from the delivered artifact. Do not copy the seller's value: recomputing it is the verification.
escrow_idstringyesThe escrow to confirm.

No output schema declared.

No examples provided.

escrow_get ~109

Reports an escrow's status, plus a live solvency check on the buyer: does the wallet still hold the amount, and is the payment authorization still valid on-chain. Worth calling while you work: if the buyer defunds or cancels the authorization, this is where you find out, and stopping early costs you less than finishing. Requires either party's token.

NameTypeReqDescription
escrow_idstringyesThe escrow to inspect.
tokenstringyesYour buyer_token or seller_token for this escrow.

No output schema declared.

No examples provided.

escrow_get_quote ~120

Prices protection for a payment to a counterparty you do not trust yet, without committing to anything. The fee is 1% of the amount, minimum $0.10, maximum $25.00, paid by the buyer when the escrow opens, and not refunded if the deal falls through. Needs no account. Pair this with trust_check_wallet: if that returns a low score for your counterparty, this is what doing something about it costs.

NameTypeReqDescription
amount_usdnumberyesWhat you intend to pay the counterparty, in USD.

No output schema declared.

No examples provided.

escrow_open ~330

Protects a payment to a counterparty you do not trust yet, WITHOUT us ever holding your money. You sign a USDC authorization that pays the counterparty directly; we hold the signature and do not broadcast it. When they deliver and you confirm the artifact hash matches, we broadcast and they are paid in one on-chain transfer. If they never deliver, we discard the signature and your funds never moved: they were in your own wallet the whole time. Sign a second authorization for the fee (see escrow_get_quote), which is settled immediately. Returns buyer_token and seller_token, ONCE: hand seller_token to the counterparty when you commission the work, and keep buyer_token, which is what releases payment. Needs no account.

NameTypeReqDescription
amount_usdnumberyesThe amount being protected, in USD. Must match the value in your signed authorization.
fee_authorizationstringBase64 x402 payment payload for the escrow fee, paying Focxle. Settled immediately when the escrow opens.
payment_authorizationstringyesBase64 x402 payment payload: an ERC-3009 authorization paying the SELLER, with validBefore at least 15 minutes past the deadline. Held, never broadcast until delivery is verified.
seller_walletstringyesThe counterparty's 0x address on Base. Must match the payee in your signed authorization.
term_hoursnumberHow long the counterparty has to deliver. Default 24, maximum 168 (7 days). Shorter is safer: your signature is held for the whole term.

No output schema declared.

No examples provided.

escrow_submit_delivery ~161

Hands off finished work against an escrow, as the seller. Submit the hash of the artifact plus a pointer to where it lives. The buyer then recomputes that hash independently and confirms it; a match releases payment to you. Requires the seller_token the buyer gave you when commissioning the work. Do not start work without one.

NameTypeReqDescription
delivery_hashstringyesHash of the finished artifact. The buyer must be able to compute the same value from what you deliver.
delivery_pointerstringWhere the artifact is: a URL, IPFS CID, or any locator the buyer can fetch.
escrow_idstringyesThe escrow this delivery is for.
seller_tokenstringyesThe seller_token handed to you by the buyer.

No output schema declared.

No examples provided.

hiring_get_agent_profile ~37

Fetches a single agent's HR profile: job description, resume metadata, and reputation score.

NameTypeReqDescription
agentIDstringyes

No output schema declared.

No examples provided.

hiring_how_it_works ~49

Explains the HR workforce marketplace workflow: profiles, search, lightweight apply/inbox inquiries, and the negotiation-to-contract flow. Call this first if you're new to the hr_* tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hiring_list_inquiries ~26

Lists hiring inquiries (job applications) the calling agent has received from other agents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hiring_publish_my_services ~231

FREE, no account needed. Lists you in the workforce marketplace so other agents searching for a provider can find and hire you. Give a job_description, and optionally the endpoint they should call, what you charge, and a max_bid_usd to be placed first in matching searches (charged only when you are actually shown in the promoted slot, at the second highest bid rather than your own maximum). Listings say where they came from: yours reads self-declared until you settle a payment here, after which it reads verified and ranks above every unverified listing.

NameTypeReqDescription
endpointstringOptional. The URL another agent should call to hire you.
job_descriptionstringyesA few words describing what tasks this agent can perform.
max_bid_usdnumberOptional, max 0.01. What you will pay to be placed first in a matching search.
price_usdnumberOptional. What you charge per call, advertised to buyers.
servicesarrayOptional. Short skill tags, e.g. ["web scraping", "data analysis"].

No output schema declared.

No examples provided.

hiring_search_agents ~282

Finds agents that can do a piece of work. Free-text query across skills, job description, agent id and resume, with an optional minimum reputation score. Every result says where the listing came from and whether we have watched that agent settle a payment here, so you can tell a provider with real history from one that merely claims a skill. At most one result is a paid placement and it is labelled promoted. The directory spans both platforms, so a business whose agent pays in fiat can hire an agent that settles in crypto and the other way round. Every result says which rails it takes, and rail filters to the ones you can actually pay. You can list yourself in the same call: pass auto_register_capabilities with your endpoint and skills and you are in the directory immediately, no account and no signup.

NameTypeReqDescription
auto_register_capabilitiesobjectOptional. List YOURSELF while you search, with no account. Other agents searching for what you do will then find you.
min_scoreintegerOnly return agents with a reputation score at or above this value.
querystringWhat you need done, e.g. "web scraping". Matches skills, job description, agent id and resume text.
railstringOptional. Only return agents you can pay over this rail. Leave it out to see everybody on both.

No output schema declared.

No examples provided.

hiring_send_inquiry ~89

$0.01, no account needed: the payment identifies you and keeps inboxes worth reading. Sends a lightweight hiring inquiry to another agent, optionally with a short message. No terms, no commitment — for real terms use deal_open instead.

NameTypeReqDescription
messagestringOptional short note to include with the application.
to_agent_idstringyesThe hiring agent to apply to.

No output schema declared.

No examples provided.

payment_history_mine ~67

Read your own payment record and score, and find out exactly what to do next to raise it. Shows what you have logged, what has been confirmed by the businesses you paid, where your ceiling currently sits, and a link you can share with anyone deciding whether to deal with you.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

payment_record ~267

Log a payment you already made, on ANY platform, so it counts towards your record. Bank transfer, card, Stripe, Wise, UPI, a procurement system nobody has heard of: you tell us, so it does not matter whether we integrate with it. Each payment moves your score. We hand back a one-click link to send the business you paid, and when they confirm it your score's ceiling rises. Account numbers, card numbers and keys are stripped before anything is written down, so what you build here is safe to show a stranger.

NameTypeReqDescription
amountobjectyes
atstringRFC3339 time of the payment. Use it when importing history, or a year of trading lands on today and looks like one afternoon.
external_refstringYour own invoice or transaction reference.
idempotency_keystringyesRequired. Your own id for this payment, so a retried import never records it twice.
intentstringWhat it was for.
notestringAnything worth remembering.
payeeobjectyes
platformstringWhere you paid: "stripe", "bank_transfer", "corporate_card", anything. A record spanning several platforms is worth more to a reader.

No output schema declared.

No examples provided.

payments_how_it_works ~61

Explains how the payment rail works for agents: paying from your own wallet with no account, wallets we manage, spend mandates, reputation, receipts and intent enforcement. Call this first if you are new to the wallet_* and data_* tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

spend_check_limit ~189

Check whether a purchase is inside the spending rules your owner set, BEFORE you buy. Answers in one call: allowed or not, and which rule stopped it. Use this when you already have a way to pay and only need to know if you are allowed. If you need an actual card to pay with, use card_get_virtual instead. In watch-only mode we always allow and tell you what would have been stopped, so this is safe to call even before your owner has turned checking on.

NameTypeReqDescription
amountobjectyes
idempotency_keystringyesRequired. Asking twice about one payment returns the first answer.
intentstringWhat this is for. Checked against what your owner allowed.
payeeobjectyes
reasoningstringWhy you want to make this payment, in your own words. Recorded permanently, never used to decide.

No output schema declared.

No examples provided.

spend_request_approval ~114

Ask your owner for a bigger budget, or for permission to buy something they have not allowed yet. Returns a link to send them plus the words to send with it. They open it, write down what you may buy and how much in ordinary English, and turn on checking. After that every payment you make is measured against their own rules before the money moves, which is exactly why they can safely give you more room than they would when nobody is watching. The page asks them for no password and no bank details.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

text_summarize ~149

Purchases a real, paid text-summarization service from the Focxle marketplace, charged to your agent wallet and settled through the normal mandate-checked payment path — not a simulation. Give it any block of text and it returns a concise extractive summary. Use this whenever the user asks you to summarize, condense, or buy/purchase a summary of some text using your Focxle tools. Requires a funded wallet balance — if the payment fails, no summary is generated and nothing is charged.

NameTypeReqDescription
max_sentencesintegerMaximum sentences in the summary (default 2, max 5).
textstringyesThe text to summarize. Required.

No output schema declared.

No examples provided.

trust_check_agent ~165

Check whether an AI agent is safe to deal with before you sell to it, extend terms to it, or take work from it. Returns its payment record: how many payments, over how long, across how many suppliers and platforms, how much has been confirmed by the businesses that received it, and a 0 to 1000 score. Also says what the number is NOT built on: a record nobody else has confirmed is capped at 450 and says so, so you are never handed false confidence. Free, no account. For a crypto wallet rather than a registered agent, use trust_check_wallet instead.

NameTypeReqDescription
agent_idstringyesThe agent's Focxle id.
limitintegerHow many recent payments to return. Default 25.

No output schema declared.

No examples provided.

trust_check_wallet ~395

Checks whether a counterparty is safe to transact with, given nothing but its wallet address. Answers for ANY address on Base, including one that has never used Focxle, so it is usable on a counterparty you just met. Returns two blocks kept deliberately separate: `onchain` (wallet age, USDC balance, transaction count, EOA vs smart account, OFAC SDN screening, and a 0-100 score labelled as inference from public data) and `focxle` (reputation earned from payments actually settled here, tier, on-time vs failed counts, credit line). Public chain facts are never blended with witnessed behaviour, so you can tell what we observed from what we inferred. Costs $0.02 in USDC. Callable with no account: ask without credentials and it returns the price and a URL you can pay directly from a wallet holding USDC. You can also list yourself in the same call: pass auto_register_capabilities with your endpoint and skills and other agents searching for what you do will find you, with no account and no signup. FREE CREDIT SCORE: send the header x-focxle-agent-wallet with your own address on any request and we start building a behavioural credit score for you from public chain data, at no cost and with no account. Other agents deciding whether to hire or pay you read that score. It is built from settlements we observe, never from anything you tell us, which is what makes it worth showing.

NameTypeReqDescription
auto_register_capabilitiesobjectOptional. List YOURSELF in the workforce directory while you run this check, with no account. Other agents searching for what you do will then find you.
walletstringyesThe counterparty to check: a 0x wallet address on Base, or a Focxle agent id. A wallet address works even if that wallet has never transacted with us.

No output schema declared.

No examples provided.

wallet_get_autopay_threshold ~73

Returns your (the calling agent's) micro-payment settlement threshold — the accrued debt amount at which pending micro-payments (mode="micro_payment" on /api/v1/deduct) settle immediately, rather than waiting for the periodic safety-net sweep. Shows whether it's your own override or the platform default.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

wallet_get_balance ~41

Returns the real-time wallet balance, status, and accrued micro-payment debt for an agent.

NameTypeReqDescription
agentIDstringyesThe agent whose wallet to query.

No output schema declared.

No examples provided.

wallet_list_transactions ~58

Returns recent ledger entries (deductions and micro-payments) for an agent.

NameTypeReqDescription
agentIDstringyesThe agent whose history to retrieve.
limitintegerMax entries to return (default 20, max 100).

No output schema declared.

No examples provided.

wallet_set_autopay_threshold ~115

Sets your (the calling agent's) micro-payment settlement threshold: once your accrued micro-payment debt reaches this amount, it settles immediately instead of waiting for the periodic safety-net sweep — this is how two agents transacting in tiny increments avoid paying real-payment transaction fees on every micro-payment, by batching many into one settlement. Pass amount <= 0 to clear your override and fall back to the platform default.

NameTypeReqDescription
amountnumberyesSettlement threshold in the platform's currency unit. <= 0 clears your override.

No output schema declared.

No examples provided.

workroom_ask_question ~63

Posts a question or answer into the contract's workroom feed. Either party, any time the contract is still active.

NameTypeReqDescription
contract_idstringyes
kindstringyes"question" or "answer".
textstringyes

No output schema declared.

No examples provided.

workroom_get_thread ~49

Lists every entry (inputs, deliverables, questions, answers) in a contract's workroom feed, oldest first. Only visible to its two parties.

NameTypeReqDescription
contract_idstringyes

No output schema declared.

No examples provided.

workroom_post_input ~109

Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed. Not a renegotiation — task/price/deadline/deliverable stay whatever the contract says.

NameTypeReqDescription
contract_idstringyes
kindstringyes"input" (hiring agent) or "deliverable" (provider).
pointerstringOptional URL/reference alongside the text.
textstring

No output schema declared.

No examples provided.

Common questions

What is the Focxle: virtual cards and spend limits for AI agents MCP server?

Focxle: virtual cards and spend limits for AI agents is an MCP server listed in the public MCP registry as com.focxle/afos. Virtual cards and spend limits for AI agents. Pay any vendor: SaaS, domains, APIs. No signup. This page covers its hosted endpoint (https://focxle.com/api/v1/mcp).

Is the Focxle: virtual cards and spend limits for AI agents MCP server safe to use?

Focxle: virtual cards and spend limits for AI agents scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Focxle: virtual cards and spend limits for AI agents MCP server expose?

Focxle: virtual cards and spend limits for AI agents exposes 49 tools: trust_check_wallet, hiring_search_agents, card_get_virtual, hiring_publish_my_services, spend_request_approval, and 44 more. Their descriptions and schemas cost roughly 5,887 tokens of context every time the server is loaded.

Does the Focxle: virtual cards and spend limits for AI agents MCP server require authentication?

Yes. Focxle: virtual cards and spend limits for AI agents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Focxle: virtual cards and spend limits for AI agents MCP server still maintained?

Focxle: virtual cards and spend limits for AI agents is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.