Sashimi2 - Fake SUSHI Provider

This is a fake COUNTER API/SUSHI provider and COUNTER 5.0 / 5.1 report generator. This server generates random usage data for testing purposes. All usage numbers are randomly generated and should not be used for any real analysis or decision-making.

Table of Contents

About This Server

This is a test server that generates fake COUNTER reports. The data is:

Platform Name Usage Types

The platform name controls which types of usage data are generated:

You can combine letters (e.g., platform=mdt for all types). If no letters are specified, it defaults to title-based usage.

AI Usage Metrics

Platforms with an 'a' in their name implement the COUNTER best practice for Generative and Agentic AI usage metrics (phase 2 draft, October 2026), an optional extension of Release 5.1. It adds the Agent Access_Method and these Metric_Types:

Metric_Type Reports
AI_Responses_Generated PR
Total_AI_Investigations, Unique_AI_Investigations PR, DR, TR, IR
Total_AI_Requests, Unique_AI_Requests PR, DR, TR, IR
Total_Retrieved_Investigations, Total_Retrieved_Requests PR, DR, TR, IR

As the best practice requires, AI usage is only included in the PR, DR, TR and IR reports (never in Standard Views), and only when it is called for using both the access_method and the metric_type filters. AI metrics are always reported against Access_Method Agent, and the requested values are listed in Report_Filters. Examples (Platform Report for platform ta, i.e. title-based usage with AI usage metrics support):

Without an 'a' in the platform name (and in all R5.0 reports), the server behaves like a platform that does not support the extension: Agent and the AI Metric_Types are ignored and reported with Exception 3060 (Invalid ReportFilter Value). The same applies to AI_Responses_Generated requested in a report other than PR.

Query Parameters

Data Report Endpoints

All data report endpoints require:

Optional parameters:

Errors and Exceptions

The api_key may also make the server return simulated errors instead of data - a Cloudflare challenge page (error:cloudflare) or any COUNTER exception (error:exception;error.code:<code>), optionally only for a part of the requests (error.rate). See Simulated Errors and Exceptions for details.

Non-Data Endpoint Parameters

Non-data endpoints have different parameter requirements:

Available Reports

COUNTER Release 5.1

Item Reports (IR)

Item Report (IR)
Journal Article Requests (IR_A1)
Multimedia Item Requests (IR_M1)

Title Reports (TR)

Title Report (TR)
Book Requests - Controlled (TR_B1)
Book Access Denied (TR_B2)
Book Usage by Access Type (TR_B3)
Journal Requests - Controlled (TR_J1)
Journal Access Denied (TR_J2)
Journal Usage by Access Type (TR_J3)
Journal Requests by YOP (TR_J4)

Database Reports (DR)

Database Master Report (DR)
Database Search and Item Usage (DR_D1)
Database Access Denied (DR_D2)

Platform Reports (PR)

Platform Report (PR)
Platform Usage (PR_P1)

COUNTER Release 5.0

Item Reports (IR)

Item Master Report (IR)
Journal Article Requests (IR_A1)
Multimedia Item Requests (IR_M1)

Title Reports (TR)

Title Master Report (TR)
Book Requests - Controlled (TR_B1)
Book Access Denied (TR_B2)
Book Usage by Access Type (TR_B3)
Journal Requests - Controlled (TR_J1)
Journal Access Denied (TR_J2)
Journal Usage by Access Type (TR_J3)
Journal Requests by YOP (TR_J4)

Database Reports (DR)

Database Master Report (DR)
Database Search and Item Usage (DR_D1)
Database Access Denied (DR_D2)

Platform Reports (PR)

Platform Report (PR)
Platform Usage (PR_P1)

Non-Data Endpoints

These endpoints provide service information and do not require date parameters.

Server Status

Returns the current status of the reporting service. This endpoint is public and does not require authentication.

Example: /r51/status

Platform List

Returns the list of platforms supported for the request credentials. This is the optional COUNTER R5.1.1 Platforms common extension. Sashimi2 generates reports for a single effective platform, so the response contains one platform with the same service description as /status.

Required parameters:

Optional parameters:

The Platform_Parameter value is the platform to use on other API paths. When api_key contains platform:Name, that name is returned; otherwise the customer ID is used (matching how reports resolve the platform).

Example: /r51/platforms?customer_id=test123

Member List

Returns the institutions associated with the customer ID. For this implementation, returns a single member derived from the customer_id.

Required parameters:

Optional parameters:

Example: /r51/members?customer_id=test123

Note: R5.0 uses Name field instead of Institution_Name in the response.

Report List

Returns the list of reports supported by the COUNTER API server for the customer. The available reports are dynamically determined based on the platform name letters (m, d, t):

If no letters are specified, it defaults to title-based usage.

Required parameters:

Optional parameters:

Examples:

Note: R5.0 reports use "Master Report" suffix in names (e.g., "Platform Master Report" instead of "Platform Report") and do not include First_Month_Available and Last_Month_Available fields.

Simulated Errors and Exceptions

Adding error:<kind> to the api_key makes every endpoint return a simulated error instead of data. This is useful for testing how SUSHI clients deal with misbehaving providers. Supported kinds:

The error can be configured further with error.<param>:<value> keys:

Simulated COUNTER exceptions

error:exception;error.code:<code> returns one of the COUNTER Release 5.1.1 exceptions (Code of Practice, Appendix D). R5.0 endpoints add the Severity field. Parameters:

Code HTTP status Behavior
1000, 1010 503 exception object is the response body; applies to all endpoints
1011 202 same as above
1020 429 same as above
1030, 3020 400 same as above
2000, 2020 401 same as above
2010, 2011 403 same as above
3030 200 report with no Report_Items
3031 200 see below
3032 200 see below
3040, 3050, 3060, 3061, 3062, 3063, 3070 200 report with the exception in its header

Exceptions with HTTP status 200 are put into Report_Header.Exceptions of report endpoints; other endpoints are not affected by them.