Tencent: 36 of 100 on Ora's agent-readiness scan

In short

Tencent scores 36 of 100 on Ora's agent-readiness scan, grade D, read on 10 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. An open door, a developer portal found only by name, and no specification behind it.

The score

Tencent is an internet and games group based in Shenzhen, the maker of WeChat.

  • 36of 100, grade D
    Ora's agent-readiness scan of tencent.com, read 10 November 2026, listed under Identity & Auth.
  • 20Discovery, of 37
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
  • 16Identity, of 40
  • 25Access, of 52
  • 8Agent Integration, of 36
  • 4User Experience, of 25

25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

The door at tencent.com
CheckResultWhat Ora saw
Not blocked by bot detectionPass, 1 of 1Site accessible to 5 AI agent user-agents
Content without JavaScriptPass, 3 of 32780 chars, semantic headings (H1 + 15 H2s + 25 H3s), 5.9% content ratio

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

Reading tencent.com
CheckResultWhat Ora saw
llms.txt existsPass, 1 of 1Found llms.txt at https://developer.tencent.com/llms.txt
llms.txt formattingPartial, 1 of 1llms.txt exists but quality could improve (8 lines, no markdown links)
Markdown agent docserror, 0 of 1Could not fetch with Accept: text/markdown
JSON-LD structured dataFail, 0 of 4No JSON-LD structured data found on homepage
Organization schema completenessFail, 0 of 1No JSON-LD found - Organization schema missing
Sitemap existsFail, 0 of 2No sitemap.xml found
Metadata completenessPartial, 1 of 2Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type
Acting through tencent.com
CheckResultWhat Ora saw
MCP server / manifestPartial, 2 of 6MCP mentioned at https://www.tencentcloud.com/document/product/1047/78210 but no standard manifest endpoint found
MCP well-known discoveryFail, 0 of 2No MCP server URL discovered
Public API with reachable endpointsPass, 7 of 7API documentation found at https://developer.tencent.com
Public API/docs linked from homepagePass, 3 of 3Documentation site found at https://developer.tencent.com
OpenAPI spec publishedFail, 0 of 7No OpenAPI/Swagger specification found
Developer portalPass, 6 of 6Developer documentation portal found at https://developer.tencent.com
OAuth 2.0 supportFail, 0 of 5No OAuth 2.0 or OpenID Connect support detected
Scoped permissionsPass, 5 of 5Scoped permissions documented at https://developer.tencent.com
Multi-language SDK packagesPass, 2 of 3SDK packages found in npm, pypi
CLI tool availableFail, 0 of 3No CLI tool found
WebMCP supportFail, 0 of 1No WebMCP support detected
Finding Tencent
CheckResultWhat Ora saw
Category share of voicePass, 5 of 6Use-case search "Chinese internet technology company services and platforms": Tencent appears prominently across multiple results with direct URL match at position #4, named as a top company in results #1, #3, and #5.
Developer resource discoverabilityPartial, 2 of 6Agent found 5 pages by name. Not found via search: API docs, OpenAPI spec, developer portal, auth docs, webhooks, MCP server

Ora probed the six payment checks and found no x402, MPP, UCP, ACP or AP2 signal, so the pay layer reads 0 of 0.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

  1. OpenAPI spec published, worth about 4.3 points by Ora's estimate: No OpenAPI/Swagger specification found.
  2. MCP Apps support, worth about 3.8 points by Ora's estimate: No MCP Apps support detected (no ui:// resources or tool UI metadata).
  3. OAuth 2.0 support, worth about 3.1 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.

Our read

Tencent's read turns on a developer portal that the rest of the site does not point to. Ora's agents found developer.tencent.com by name, with API documentation, an llms.txt of 8 lines without links, scoped permissions described in prose and SDKs on npm and PyPI, but a search for the company's API docs, developer portal, auth docs and MCP server returned nothing, and the MCP that is mentioned sits in a Tencent Cloud document with no standard manifest. The door is open: the site was accessible to all 5 agent user agents tested. What they can read is 2,780 characters with an H1, 15 H2s and 25 H3s at a 5.9 percent content ratio, with no sitemap, no JSON-LD and 1 of 4 metadata signals. What they can do is little, and Agent Integration reads 8 of 36: neither an OpenAPI specification nor OAuth, the two fixes worth most. A D at 36 for a company whose developer documentation exists and whose home page keeps it a secret.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for tencent.com; a scan of a public site takes a few minutes and needs no account.

Sources

  1. Ora report for tencent.com (ora.ai/score/tencent.com), read 10 Nov 2026. Vendor claim.

Last reviewed