ARI Award 2027 Global is scored with this document, together with the "Search procedure" and the "Casebook" below. Graders and reviewers use nothing else. The method was written in Japanese; this is a translation.
.well-known returns JSON and nothing more) does not make it 20.
| Format | What is checked |
|---|---|
| OpenAPI 2.0 / 3.x | paths contains the operation in scope, and its parameters or responses have types (schema) |
| GraphQL | A published schema file (SDL or an introspection result) contains types and operations. It is not obtained by querying the endpoint |
| Google Discovery document | It has operations (methods) and types (schemas) |
| WSDL (SOAP) | It has definitions of operations and types |
| gRPC proto | It has definitions of services and messages |
| RAML, API Blueprint, JSON Hyper-Schema | It has operations (URL and method) and types |
| AsyncAPI | It has operations and message types. A notification-only specification still earns 20 on B2, but by itself earns nothing on A1 or B1 |
| Postman collection | Published under the vendor's name, with a saved example input and example response for each operation (accepted in place of types) |
| JSON examples or a CSV field list and nothing else | Not counted |
Listing on the official MCP Registry / whether the MCP is remote or local / preview or beta / plan and region required / MCP for documentation / connectable through an aggregator / automated retrieval refused / language of the documentation / published after contract / application or review required (the reason the company states) / kind of test environment / format of the specification / use tags / that the provider is a third party.
"None" may be written when all the steps for that item have been finished, and not before. If they are not finished, "not confirmed". The places searched and the search terms are recorded for each row.
For the product's name, the "product name", "other names" and "domain" in the scope table are used.
.well-known, and resource_metadata in a response header); (4) URLs of specification files that appear in the response of a public page or in what it loads. If it cannot be obtained, "not confirmed".
"<product name>" API / "<product name>" developer documentation (for Japanese products, "<product name>" API 連携 開発者) / "<product name>" MCP.
llms.txt if there is one). The terms may be searched together.
/v0.1/servers and metadata.nextCursor) with the main words of the product name, the company name and the domain. Fetch until there is no nextCursor, then narrow by namespace and product name.
<product name> mcp and the GitHub search <product name> mcp server. For up to the top 10 results, open the README of those whose name and description read as "an MCP for that product". When the GitHub search hits its rate limit, the web search "<product name>" mcp server github is used in its place.
/.well-known/oauth-protected-resource (at the root and with the path) and the metadata of the authorization server it points to. When the endpoint differs per user or per shop, it is confirmed from what the documentation says.
Cases are added as rulings are made in the main scoring. Each keeps its number, the point at issue, the ruling and the products it was applied to. The five cases below were decided in advance from borderline examples that came up in the trial scoring. They are settled once the evidence is confirmed in the main scoring, and the names of the products they were applied to are published together with the results.
| No. | Point at issue | Ruling | Products applied to |
|---|---|---|---|
| C-001 | The description of a third-party MCP and the material of the cloud edition in scope disagree | When there is a disagreement about the applicable conditions, the authentication or the supported version that cannot be resolved, that A1 or A2 is "not confirmed". Nothing is run to check it | Listed when the results are published (2027-01-20) |
| C-002 | An asset that needs an additional contract | Not counted until that contract is written in the scope table and given to every grader | Listed when the results are published (2027-01-20) |
| C-003 | A connection operated by the customer's own customers, such as shoppers | A connection that handles the orders and customer data of the product in scope goes into A1 even when the person operating it is the customer's customer. Who operates it is written in the information column | Listed when the results are published (2027-01-20) |
| C-004 | An MCP that operates the product in scope through another product's API | If concrete business operations on the product in scope can be confirmed from the material, going through another product's API is not by itself a reason to leave it out (the aggregator rule is applied separately) | Listed when the results are published (2027-01-20) |
| C-005 | A specification inside a distribution package | A complete specification inside a package that the official documentation points to is a candidate for B2. When it cannot be confirmed to apply to the version of the API taken, "not confirmed" | Listed when the results are published (2027-01-20) |