日本語 | Contact
ARI Award 2027 Global

日本語版

Scoring method v1.5 (full text), search procedure and casebook

Scoring method Search procedure Casebook

Scoring method v1.5 (2026-11-19)

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.

0. What is measured and what is not

1. The unit of scoring

2. Scale A (90 points)

A1 Connection

A2 Authentication (of the route taken in A1)

A3 Developer documentation (10)

A4 Distribution (10)

3. Scale B (90 points)

B1 API reference (30)

B2 Machine-readable specification (20)

FormatWhat is checked
OpenAPI 2.0 / 3.xpaths contains the operation in scope, and its parameters or responses have types (schema)
GraphQLA published schema file (SDL or an introspection result) contains types and operations. It is not obtained by querying the endpoint
Google Discovery documentIt has operations (methods) and types (schemas)
WSDL (SOAP)It has definitions of operations and types
gRPC protoIt has definitions of services and messages
RAML, API Blueprint, JSON Hyper-SchemaIt has operations (URL and method) and types
AsyncAPIIt has operations and message types. A notification-only specification still earns 20 on B2, but by itself earns nothing on A1 or B1
Postman collectionPublished 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 elseNot counted

B3 Self-serve credentials (20 / 10 / 0)

B4 Test environment (10)

B5 Official SDK or CLI (10)

4. States and records

5. Grades, ranges, badges and the entry classification

6. Reference date

7. Information column (not scored)

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.

8. Comparison with Summer (ARI Award 2026 Summer)

9. Disclosure of relationships, and limits

10. How the main scoring proceeds (two graders, rulings, casebook)

Search procedure (everyone searches by the same steps; 2026-11-19)

"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.

0. Rules to keep

1. Finding the entry point (every product)

2. MCP (A1)

3. Public API (A1, B1)

4. A2

5. A4

6. B2

7. B3

8. B4

9. B5

Casebook (as of 2026-11-19)

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 issueRulingProducts applied to
C-001The description of a third-party MCP and the material of the cloud edition in scope disagreeWhen 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 itListed when the results are published (2027-01-20)
C-002An asset that needs an additional contractNot counted until that contract is written in the scope table and given to every graderListed when the results are published (2027-01-20)
C-003A connection operated by the customer's own customers, such as shoppersA 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 columnListed when the results are published (2027-01-20)
C-004An MCP that operates the product in scope through another product's APIIf 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-005A specification inside a distribution packageA 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)