> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/performance-benchmarks/staff-api.md).

# Staff API

Performance-testing plan, execution, and results for the staff-api (`staff-portal-api`) service — the highest-traffic surface in the registry.

## Test Scenarios

The test plan: objectives, scope, the Volume-Tier × Pod-Scale model, the 5 Locust scenarios, SLOs, and the execution runbook.

{% content-ref url="/pages/MaXwlUdbvkRNLSZRFMat" %}
[Test Scenarios](/products/registry/registry/performance-benchmarks/staff-api/test-scenarios.md)
{% endcontent-ref %}

## Raw Report

Every measurement Locust actually recorded, verbatim — auto-generated, no interpretation.

{% content-ref url="/pages/RKakDETcxptid02Y9EWg" %}
[Raw Report](/products/registry/registry/performance-benchmarks/staff-api/raw-report.md)
{% endcontent-ref %}

## Final Report

The interpretation layer: capacity/sizing model, bottleneck findings, and pass/fail against the SLOs — built from the raw report.

{% content-ref url="/pages/ZWW04YTl97fwND4WMl2Y" %}
[Final Report](/products/registry/registry/performance-benchmarks/staff-api/final-report.md)
{% endcontent-ref %}

## Final Report Summary

A condensed version of the final report: methodology, data seeding, and headline results.

{% content-ref url="/pages/18RzDmTGZRAlP0KP2OEQ" %}
[Final Report Summary](/products/registry/registry/performance-benchmarks/staff-api/final-report-summary.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/products/registry/registry/performance-benchmarks/staff-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.