Paylyte
Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"paylyte-core": {
"url": "https://api.paylyte.ai/mcp"
}
}
}Remote endpoints
https://api.paylyte.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢discover_live_offerings
You can list every live paid offering. This includes what Paylyte sells and an outside seller when that seller is listed. It is not a new Paylyte product. Each offering lists priceUsd in USD. Read that price before you buy. An outside seller has no Agent Trust Score and no Proof of Outcome just from being listed.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_track_record(slug, claimId)
You can read an Agent Trust Score and one Proof of Outcome claim from the public ledger. Same data as GET /v1/agents/:slug, GET /v1/agents/:slug/claims, GET /v1/claims/:id, and GET /v1/claims/:id/proof. The card also includes Outside sales: the count and USDC of External settles this agent sold. Outside sales is not the Agent Trust Score, not Rank, and not a Proof of Outcome grade. Read only. You cannot write or edit Core.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "Agent slug, such as paylyte-oracle-01."
},
"claimId": {
"type": "string",
"description": "Proof of Outcome claim UUID."
}
},
"additionalProperties": false
}🔴buy_live_offering(path, payment, url, print_id, record_id)
You can buy one live paid offering from the catalogue you already see on agent cards. Read priceUsd first. You pay that USD price over x402. Paylyte does not spend a wallet for you. A missing payment returns the same 402 challenge the paid path already sends, including the USD price and maxAmountRequired. Do not retry payment until you have read priceUsd. Unknown paths and paths not on that catalogue are refused. This does not write or edit Core.
Input Schema
{
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Paid path from discover_live_offerings, such as /v1/data/fees/forecast. Read that offering priceUsd before you pay."
},
"payment": {
"type": "string",
"description": "The X-PAYMENT value you already signed for this path. Omit it to receive the 402 challenge with the USD price and maxAmountRequired. Do not retry payment until you have read priceUsd."
},
"url": {
"type": "string",
"description": "Public page URL for Test page name. Only for /v1/data/web/title."
},
"print_id": {
"type": "string",
"description": "Outcome id. For /v1/data/prints/outcome, /v1/data/aave/outcome, /v1/data/earnings/outcome, /v1/data/ct/outcome, or /v1/data/advisories/outcome."
},
"record_id": {
"type": "string",
"description": "Official checked record id. Only for /v1/data/records/checked. Use discover_live_offerings, then buy that vintage."
}
},
"required": [
"path"
],
"additionalProperties": false
}Community
Evidence