369 Meter — pay-per-call APIs for agents (x402)
Pay-per-call APIs for agents: text analysis, game facts, translation QA, hook scoring via x402.
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": {
"meter369": {
"url": "https://369yz.pythonanywhere.com/meter/mcp"
}
}
}Remote endpoints
https://369yz.pythonanywhere.com/meter/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢text_analyze(text)
Use this when you need deterministic text analysis (counts, Flesch readability, script mix, top keywords). Pay-per-call: $0.01 USDC on Base via x402 to the REST route POST /v1/text/analyze.
Input Schema
{
"type": "object",
"properties": {
"text": {
"type": "string",
"description": "Text to analyze, up to 20000 chars"
}
},
"required": [
"text"
]
}🟢hook_score(headline, platform)
Use this when you need a gaming headline or hook scored 0-100 against the 369 team's hook rules. Pay-per-call: $0.01 USDC on Base via x402 to the REST route POST /v1/hook/score.
Input Schema
{
"type": "object",
"properties": {
"headline": {
"type": "string",
"description": "Headline/hook to score"
},
"platform": {
"type": "string",
"description": "Optional platform, default 'reels'"
}
},
"required": [
"headline"
]
}🟢translate_check(source_text, target_text)
Use this when you need an EN<->FA translation QA score 0-100 (numbers/entities preserved, script purity, untranslated segments). Pay-per-call: $0.02 USDC on Base via x402 to the REST route POST /v1/translate/check.
Input Schema
{
"type": "object",
"properties": {
"source_text": {
"type": "string",
"description": "Source text"
},
"target_text": {
"type": "string",
"description": "Translated text to check"
}
},
"required": [
"source_text",
"target_text"
]
}🟢game_facts(query, limit)
Use this when you need live game metadata from RAWG (release date, ratings, Metacritic, platforms, genres). Pay-per-call: $0.03 USDC on Base via x402 to the REST route POST /v1/game/facts.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Game title to look up"
},
"limit": {
"type": "integer",
"description": "Optional, 1-5, default 3"
}
},
"required": [
"query"
]
}Community
Evidence