AgentPay
com.myuiafPublished by myuiaf.comOfficial publisherv1.0.0Updated Nov 8, 2026
Let agents pay for third-party APIs per call from one prepaid wallet. Charged only on success.
The publisher's own server: AgentCache
Overview
A remote MCP endpoint that lets an AI assistant pay for third-party API calls per use from a single prepaid wallet, charged only when a call succeeds.
- What you can do
- The manifest lists no tools, so capabilities come from the short description only.
- Pay for third-party API calls per call from one prepaid wallet.
- Calls are charged only on success, so failed calls are not billed according to the description.
- Access is authenticated with a myuiaf API key sent in the Authorization header.
- When to use it
- Consider it when an assistant needs to call paid third-party APIs and you want a single prepaid balance with per-call billing instead of separate provider accounts. It is not useful if you only need free APIs or already have direct provider billing.
- Requirements
- A remote endpoint at agentpay.myuiaf.com over streamable HTTP, with OAuth authentication. A myuiaf API key is required in the Authorization header, and credits must be purchased beforehand. No packages or environment variables are declared.
Installation
In SourceWeft
- Open AgentPay in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.myuiaf%2Fagentpay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"agentpay": {
"type": "http",
"url": "https://agentpay.myuiaf.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestNov 8, 2026
Score
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
Other Myuiaf integrations
AgentCache
com.myuiafOfficial publisher
AgentCache is a remote semantic answer cache that lets an assistant reuse cached answers to repeated or reworded questions, billed per hit.
Freshness Validator
com.myuiafOfficial publisher
Remote MCP server that scores how stale an AI agent's context is (0-100) and detects changes in its sources.