BlockRun.AI vs Tencent Cloud TokenHub

BlockRun.AI 100

x402 v2 on its own gateway, USDC on Base and Solana, and since MCP 0.55.0 (28 October) on Circle's Arc through arc.blockrun.ai (40). Per-token prices per model published without a login, plus a flat $0.001 fee per wallet call on Base (20). Seven free models per the status page's menu, no card or sign-up, and a wallet costs nothing to create (20). An agent can create its own wallet and pay per request with no human sign-up (20). 40 + 20 + 20 + 20 = 100.

Tencent Cloud TokenHub 35

No x402, MPP or L402 (0). Per-token prices for every model are public in CNY for Guangzhou and Singapore, with DeepSeek's peak and off-peak rates (20). Each account gets 1M free tokens per language model, valid for a year, in a campaign running to 31 December 2026. No card is mentioned, but the account needs real-name verification, so this line takes 15 of 20. A person signs up and completes real-name verification in a browser. Keys can then be created in code or by thcli auth login, but only from that account (0).

BlockRun.AI 65

Read with the local-software lines, as the listing's kind is mcp and the owner runs the server over stdio, though every paid call lands on BlockRun's gateway (the reading assymetrix-mcp and copilot-studio-mcp get). The 1 October check read it as a router. Installs from the official npm package @blockrun/mcp with Node 20.19 or later stated in engines (20). The CI workflow runs typecheck, build and tests on Node 20.19 and 22 on every push and pull request, with a required gate job. Run results weren't readable, as GitHub's pages answered 403 (20 of 25). Open issues couldn't be read. The changelog names numbered reports fixed in releases, such as #176 and #177 in 0.54.3 and 0.54.4 (10 of 25). Semver numbering with breaking changes marked BREAKING in CHANGELOG.md and shipped as minor bumps, as its own entries say (15). Version 0.55.0, pre-1.0 (0). 20 + 20 + 10 + 15 + 0 = 65. For the gateway behind it, blockrun.ai/status still shows live checks of the Base and Solana gateways and says "None recorded on this page yet" under incident history, the terms still say "We do not commit to any particular uptime", and free models are limited to 30 requests a minute and 300 an hour per IP with 429s carrying Retry-After.

Tencent Cloud TokenHub 46

Hosted reading. No public status page was found. status.cloud.tencent.com did not answer and the Tencent Cloud health dashboard documentation answered with a bot check (0). With no page there is no incident record to read (5 of 30). The announcements carry one incident, DeepSeek's directly supplied models unavailable from 9:06 to 13:04 Beijing time on 15 October 2026 after a fault at DeepSeek, compensated with vouchers. Rate limits are per model, shown in the console and returned by DescribeModelQuota. The public docs give numbers only for batch jobs (20 created a minute, 10 active), image models (5 concurrent) and DeepSeek V4 Flash and Pro (2,500 and 500 concurrent), with the rules for self-serve increases (8 of 15). Six 429 codes separate RPM, TPM, TPD, concurrency and upstream capacity, 429s may carry Retry-After and the docs advise exponential backoff. No idempotency guidance, though inference calls are not writes (13 of 15). The TokenHub SLA promises 99.5% monthly availability with vouchers of 10, 25 or 50 per cent of the month's fee. It excludes free use and third-party deployed models such as DeepSeek's directly supplied ones (10). Generally available since 7 April 2026, with some models marked preview (10).

BlockRun.AI 73

The editorial half. The MCP server and SDKs are MIT and the gateway is closed. The listing is graded as the MCP server, so 30 as assymetrix-mcp got for an MIT server in front of a closed API (was 15 under the router reading). The terms and privacy policy, both last updated 21 October 2026, now name the same entity, BlockRun, Inc., as contracting party and data controller. The privacy policy now says prompts, completions and tool calls to blockrun.ai, arc.blockrun.ai, nano.blockrun.ai and api.blockrun.ai are stored with the paying wallet or account and kept "until we delete it; it has no fixed expiry", usage records and connection metadata for 13 months, while the Solana gateway keeps no request content. The 1 October policy said prompts weren't stored past the request and metadata was kept 30 days. The documents agree with each other, but content has no retention period and no subprocessors are named (18 of 30, was 20). No deprecation policy, and the terms say a provider may withdraw a model at any time. Removals are dated in the changelog, such as Gemma 4 31B delisted on 2 October, the same day (5 of 20). Upstream providers are named and Google Analytics is disclosed with its cookies and retention. Data locations aren't stated, and whether the MCP server sends telemetry wasn't read (10 of 20). 30 + 18 + 5 + 10 = 63.

Tencent Cloud TokenHub 54

Closed service under the TokenHub Terms of Service (effective 14 September 2026), the SLA (23 April 2026), a special note on third-party deployed models and the Tencent Cloud Service Agreement, naming Tencent Cloud Computing (Beijing) Co., Ltd. The CLI is Apache-2.0 (18 of 30). The terms and the FAQ agree that inputs are processed on the customer's instructions and not used for training, and clause 2.14 limits retention to what the service needs without periods. The TokenHub privacy policy on privacy.qq.com renders only with JavaScript and was not read (15 of 30). Dated retirement notices, shutdown dates in the model list, a pre-offline status in /v1/models and a DiscontinuedAt field in the control API. Clause 6.3 refunds paid, unused tokens when a third-party model is removed. No minimum notice period is written (13 of 20). Clause 2.13 places processing generally in mainland China for the China site and in Singapore for the international site, and the third-party model list names DeepSeek's Hangzhou company with a link to its terms. No subprocessor list was found (13 of 20).

BlockRun.AI 90

MCP reading. All 19 tools take zod input schemas, which the MCP SDK turns into JSON Schema, per the 1 October read of the source (25, was 10 for the gateway's OpenAPI document, which robots.txt still keeps our reader out of under /api/). llms.txt served at blockrun.ai/llms.txt (10). The tool descriptions state purpose and order of use, such as 'discover markets ... with blockrun_markets first' and 'Run action:"setup" FIRST', per the 1 October check (15 of 20). Enums and numeric bounds, but seven fields across six tools take a free-form z.any() JSON body, per the 1 October check (10 of 15). The docs have an error reference with codes per status and recovery steps, and the README has examples for each client (15). A dated gateway changelog, last entry 25 October 2026, and a CHANGELOG.md in the MCP repository through 0.55.0 (15). 25 + 10 + 15 + 10 + 15 + 15 = 90.

Tencent Cloud TokenHub 73

Router, scored on the API lines. No OpenAPI file for the inference routes. Field pages document the OpenAI Chat Completions, OpenAI Responses and Anthropic Messages formats as TokenHub implements them, and the control plane is a Tencent Cloud API 3.0 service (version 2026-03-22) with typed parameters, API Explorer and SDKs (12 of 25). An llms.txt at cloud.tencent.com/document/product/1823/llms.txt links a Markdown copy of each docs page (10). The docs say which models support thinking, tools, structured output and caching, how TokenHub departs from each standard protocol, and which DeepSeek model suits which job. The quickstart's examples still use deepseek-v3, which is not in the model list, and Qwen3.5 stays in the list with a past shutdown date (13 of 20). Protocol pages list each field with type, required flag and default, and control-plane parameters carry enums and required flags (10 of 15). Examples in curl, Python, Node.js, Java and Go, and an error page listing 30 codes with HTTP status, cause and fix (14 of 15). Paths carry /v1, release notes are dated monthly from 7 April to 24 October 2026, and the control-plane API has a dated history of 26 releases to 18 September 2026 (14 of 15).

BlockRun.AI 85

MCP reading. @blockrun/mcp 0.55.0 published to the official MCP registry on 28 October 2026, and a gateway changelog entry on 25 October (30). 40 registry versions from 0.35.0 on 3 August to 0.55.0 (20). Issue replies couldn't be read, as GitHub's issue pages answered 403; the changelog credits numbered reports fixed within releases (10 of 25). Listed in the official MCP registry as io.github.BlockRunAI/blockrun-mcp, a GitHub-verified namespace, active, with 0.55.0 marked latest (15). CI on Node 20.19 and 22 with typecheck and tests on every pull request, and a Renovate configuration in the repository (10). 30 + 20 + 10 + 15 + 10 = 85.

Tencent Cloud TokenHub 73

Closed service, read on the model lines. The newest release note is dated 24 October 2026 and the price page was updated on 31 October (30). The four retirement notices read gave 21 to 33 days, and eligible callers are switched to a successor at its price. No minimum notice period is written, and DeepSeek-V4.1-Flash (directly supplied) was moved to the 1017 version under the same ids on 17 October 2026 in a notice dated two days later (7 of 12). 18 retirement notices from 21 April to 22 October 2026, 12 of them since 3 August (3 of 8). Dated release notes and announcements, ticket and phone support around the clock and a Q&A community (13 of 15). Replies on the THCLI repository were not sampled (3 of 10). Tencent Cloud SDK 3.0 in several languages covers the control plane and tencent-tokenhub-cli 1.0.2 was published on 30 October 2026. No inference SDK of its own (12 of 15). The CLI has four releases since 15 September 2026, lists no runtime dependencies and needs Node.js 18 or later. CI not checked (5 of 10).

BlockRun.AI 61

MCP and API reading. The credential is a wallet private key, auto-created at ~/.blockrun/.session or passed in an environment variable and optionally mirrored to the OS keychain, and it controls the whole balance. blockrun_wallet can delegate a capped budget to a child agent, and an API-key route backed by account credit exists (20 of 30, as on 1 October). blockrun_polymarket_read gives read-only positions and previews apart from the trading tool, trades need confirm:true with a $25 default order cap, --profile drops whole groups of tools, and BLOCKRUN_CONFIRM_SPEND=on pauses every paid call for approval, though it's off by default (16 of 20). Search, Exa, market and RPC tools return third-party content, and no prompt-injection guidance was found in the README or docs read (5, as knock and suprsend). Every payment settles on-chain and the wallet tool reports balances and spending (10 of 15). security.txt is valid on 1 November, with an email contact, a policy link and an Expires date of 1 November 2027, and SECURITY.md takes private GitHub reports with a 72-hour acknowledgement and a 7-day plan for fund-affecting issues. No bounty or certification found (10). 20 + 16 + 5 + 10 + 10 = 61.

Tencent Cloud TokenHub 71

Router, read on the model lines. Bearer keys can be limited to chosen models and inference services, up to 200 source IP ranges and daily, monthly or total token quotas, can be disabled or deleted, and can be created in code through CreateApiKey with signed Tencent Cloud credentials. Keys are long-lived with no expiry setting or built-in rotation (26 of 30). Clause 2.17 of the terms says inputs are not used to train Tencent Cloud's own models, and the FAQ says data is not used for training. Inputs to third-party deployed models (DeepSeek's directly supplied ones) go to DeepSeek under its terms (14 of 20). Clause 2.14 keeps data only as long as the service needs, with no periods stated. When a customer asks for generated content without AI labels, Tencent Cloud keeps logs of who received it for at least six months. No zero-retention option was found (7 of 15). Per-call audit logs (request ID, key, client IP, status, tokens, latency) and optional full call logs go to the customer's CLS, billed separately, with usage by key and a monitoring dashboard (14 of 15). No security.txt on cloud.tencent.com, www.tencent.com or tokenhub.tencentmaas.com (404). Tencent's bug bounty through TSRC lists Tencent Cloud in scope. No certification for TokenHub was checked (10 of 20).