Simulation: FrontierOrg is a fictional infrastructure holding group; figures are fixtures or marked not measured, and no vendor sponsors this work.

Lab capability · not a product

Judge the state. Do not invent the score.

This page records how the open methods lab may use BeatAPI. It is not a product, a procurement, or a vendor endorsement. BeatAPI is a third-party API. No vendor sponsors this work. A catalogue count is not a FrontierOrg result.

Methods Repository

Last verified: loading the snapshot…

How a call is made

Agents call REST at https://api.beatapi.io. The credential is a private bearer token on the agent host. It is not in this repository. This page does not have it. The page only fetches the static file data/beatapi-catalogue.json.

The browser never holds the key. It does not send an Authorization header. Scoring, if it is ever run, happens on the agent side and may write a result file. That file may hold answers and request ids. It must not hold the key. This page does not start a run. A paid run needs an explicit ask. See the maintainer note.

What the lab would use it for

Sample data stays in this repository. Generators and fixtures are the evidence. BeatAPI is not a data warehouse for FrontierOrg and it is not a measured outcome.

  1. Decisions. model:jev-1.13-free takes a written state and typed questions. It returns typed answers. It does not generate prose. A go, revise, or stop judgment can be posed as a choice. The answer is not a board minute, not a benefit, and not a cell on the scorecard.
  2. Web research. The catalogue includes a web search and read group. A fetched page is untrusted text. It does not become a diary fact unless a person writes it and the diary words are approved.
  3. Optional scoring. A score question type exists. We do not use it to invent an enablement index, a return on investment, or a percentage the fixture does not support. Actuals stay not measured.

Pause beats a fake win. If the state cannot be grounded in a fixture or an approved note, the question is not asked. Cost, risk, and engagement and enablement stay in the same view. A model reply does not close an issue.

Inspected capability

The snapshot inspects model:jev-1.13-free (JEV decisions, free tier). Required inputs are state and questions. Question types in that schema are noul, choice, and score. Execution is synchronous: the answer comes back on the response. The snapshot price is zero US dollars per million tokens. That is a snapshot of a free tier, not a live quote and not permission to run it from the browser.

FrontierOrg would pass the state as text or JSON the diary already stands behind, and name the questions in the same call. The schema rejects unknown fields. We would not add a hidden field to smuggle a conclusion. We would not copy an answer into a board pack and call it measured.

Schema detail loads with the snapshot.

Snapshot catalogue

Tables below are rendered from data/beatapi-catalogue.json. If that file does not load, the tables stay empty. This page will not invent a catalogue.