Head to head · LLM inference · October 2026 research run

BlockRun.AI vs Tencent Hy4

BlockRun.AI scores 78.9 (A) on agent readiness against Tencent Hy4's 64 (B), and leads in 6 of 7 scored categories. Tencent Hy4 leads on security & auth. Both do llm inference. BlockRun.AI accepts x402. Tencent Hy4 doesn't.

Best model APIs and inference for AI agents · All 1044 models comparisons

Which one, for what

BlockRun.AI A

Best for Agents that must start and pay with no human sign-up, and builders testing x402 against a real inference gateway.

Ahead on

  • Reliability, 65 against 46
  • Schema & documentation, 90 against 73
  • Payments & pricing, 100 against 45
  • Maintenance & community, 85 against 73
  • Transparency & trust, 73 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • An agent can pay per call over x402, with no account
  • Runs on your own machine

Watch for

Since 21 October 2026 prompts and completions sent through the Base, Arc and API gateways are stored with no fixed expiry

Tencent Hy4 B

Best for Long-context agent work, coding and office or finance tasks on a 1M-token context with images, for teams already on Tencent Cloud or happy to verify an account there.

Ahead on

  • Security & auth, 71 against 61

Watch for

Weights, licence and system card are promised but not published; tencent/Hy4 didn't answer on Hugging Face on 11 November

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing BlockRun.AI +55

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. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 60 is 90 at 30 each, so 100 is 100.

Tencent Hy4 45

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. No machine payment protocol (0). The price page, updated 9 November, lists ¥6 input, ¥0.3 cached and ¥18 output per million tokens, with Hy4 billed at 50% until 31 December 2026 (20). TokenHub's campaign of 1M free tokens per language model, read on 1 November, isn't confirmed for hy4 on the price page, so half (10 of 20, a judgement call). A person signs up with real-name verification (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust BlockRun.AI +21

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 Hy4 52

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service under the TokenHub terms, but Tencent's release headline calls Hy4 open source while the weights and system card are only promised 'in the coming days', with no licence stated, and tencent/Hy4 didn't answer on Hugging Face on 11 November (14 of 30). Terms and FAQ agree inputs aren't used for training; the privacy policy renders only with JavaScript and wasn't read (15 of 30). Dated retirement notices and shutdown fields (13 of 20). Processing generally in mainland China for the China site, Singapore for the international one (13 of 20). Every benchmark in the release is Tencent's own or a partner's. 14 + 15 + 13 + 13 = 55.

Reliability BlockRun.AI +19

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 Hy4 46

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. No public status page (0) and so no incident record to read (5 of 30). Per-model rate limits only in the console and DescribeModelQuota (8 of 15). Six 429 codes, Retry-After and backoff advice (13 of 15). The TokenHub SLA promises 99.5% a month, and Hy4 is Tencent's own model, so the third-party exclusion doesn't apply (10). Released as hy4 on 4 November, a separate id from hy4-preview, with no preview label (10). 0 + 5 + 8 + 13 + 10 + 10 = 46.

Schema & documentation BlockRun.AI +17

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 Hy4 73

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. No OpenAPI file for inference; field pages for the OpenAI and Anthropic formats as TokenHub implements them (12 of 25). llms.txt with Markdown copies (10). The model list, updated 9 November, gives hy4's context, input and output limits and marks thinking, structured output, function calling, caching and image understanding; computer use, which Tencent's release names, isn't marked (13 of 20). Typed field pages (10 of 15). Examples in five languages and an error page of 30 codes (14 of 15). Dated release notes, with hy4 added on 4 November (14 of 15). 12 + 10 + 13 + 10 + 14 + 14 = 73.

Maintenance & community BlockRun.AI +12

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 Hy4 73

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Added on 4 November 2026 per the release notes; the model list and price page were updated on 9 November (30). Retirement notices of 21 to 33 days, no minimum written (7 of 12). Heavy retirement churn on the platform (3 of 8). Dated release notes and announcements, round-the-clock support (13 of 15). CLI replies not sampled (3 of 10). Control-plane SDKs and CLI, no inference SDK of its own (12 of 15). CLI runtime stated, CI not checked (5 of 10). 30 + 7 + 3 + 13 + 3 + 12 + 5 = 73. The model is a week old, so these lines are TokenHub's habits more than Hy4's record.

Security & auth Tencent Hy4 +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 Hy4 71

Model reading for hy4 on Tencent Cloud TokenHub. Platform facts are the tencent-tokenhub listing's (checked 1 November), carried over as RULES.md allows for a model on an already graded platform. Bearer keys limited by model, service, IP range and token quota, long-lived with no rotation (26 of 30). The terms say inputs aren't used to train Tencent Cloud's own models, and Hy4 is first party, so no third party's terms apply (14 of 20). Retention only as long as the service needs, no periods (7 of 15). Per-call audit logs and optional full logs to the customer's CLS (14 of 15). No security.txt; Tencent's TSRC bounty covers Tencent Cloud; no certification checked (10 of 20). 26 + 14 + 7 + 14 + 10 = 71.

Score by category

CategoryWeight this runBlockRun.AITencent Hy4Edge
Reliability16%206546BlockRun.AI +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29073BlockRun.AI +17
Agent ergonomics13%16.28886BlockRun.AI +2
Security & auth14%17.56171Tencent Hy4 +10
Payments & pricing10%12.510045BlockRun.AI +55
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88573BlockRun.AI +12
Transparency & trust7%8.87352BlockRun.AI +21
Negative events≤1500
TotalA 78.9/100B 64/100

Facts side by side

FactBlockRun.AITencent Hy4
KindMCP serverModel API
VendorBlockRun, Inc.Tencent (Hy team)
Hosted endpointno (local only)no (local only)
TransportsstdioHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402yesno
LicenceMITHosted model under the Tencent Cloud TokenHub terms. Tencent says weights and a system card will follow; no licence is stated yet
Tools exposed19none
Read-only variant documentedyesno
llms.txtyesyes
MCP registryio.github.BlockRunAI/blockrun-mcpnot listed
Last release2026-10-282026-11-04
Terms last updated2026-09-02couldn't be read
Privacy policy last updated2026-09-02couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity5 stars, 679 PyPI/wknone
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

BlockRun.AI

x402 v2 on its own gateway lets an agent create a wallet and pay per call in USDC on Base, Solana or Arc with no sign-up, and every MCP tool carries a safety annotation. Since 21 October 2026 prompts sent through the Base and Arc gateways are stored with no fixed expiry, and the status page keeps no incident history.

Tencent Hy4

Tencent's flagship model is on TokenHub as hy4, with a 1M-token context, image understanding, function calling and caching, at ¥6 input and ¥18 output per million tokens, half price until the end of 2026. The weights it is called open source for aren't published yet, and every benchmark is Tencent's own.

Before you call either

BlockRun.AI

  1. Fund a dedicated wallet with a small USDC balance. The balance is the spending cap
  2. Use the Solana gateway when prompts must not be stored. Base and Arc keep request content with no fixed expiry
  3. Start the server with --profile for the job (chat, research, media or trading) to cut the tool definitions
  4. Set BLOCKRUN_CONFIRM_SPEND=on to approve each paid call. It's off by default
  5. Call blockrun_models before hard-coding a model name, since models are removed without notice

Tencent Hy4

  1. Use model id hy4 on TokenHub's OpenAI- or Anthropic-compatible endpoints; hy4-preview is a separate, older model
  2. Keep input under 960K tokens and expect at most 64K output
  3. Reuse prompt prefixes: cached input is ¥0.3 against ¥6
  4. Check the price page for the end of the 50% discount on 31 December 2026 before budgeting
  5. Read rate limits from the console or DescribeModelQuota; the public docs don't give them for chat models

Questions

Which is better for AI agents, BlockRun.AI or Tencent Hy4?

BlockRun.AI scores 78.9 (A) on agent readiness against Tencent Hy4's 64 (B), and leads in 6 of 7 scored categories. Tencent Hy4 leads on security & auth.

Do BlockRun.AI and Tencent Hy4 need an API key?

BlockRun.AI takes an API key or an OAuth sign-in. Tencent Hy4 needs an API key. An agent can also pay BlockRun.AI per call over x402, with no account.

Can an agent call BlockRun.AI and Tencent Hy4 without installing anything?

BlockRun.AI runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Tencent Hy4.

Other comparisons with BlockRun.AI or Tencent Hy4

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.