# Get Quality History

> Get Quality History is a paid API for AI agents from agents.forwardlane.com, paid per call via MPP, $0.05/call, status unknown (last checked 2026-10-10).

Returns a time-series of code quality scores for a specified financial-services repository over a configurable number of days.

## Facts

- Endpoint: GET https://agents.forwardlane.com/api/quality/history?utm_source=zero.xyz
- Price: $0.05/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Provider: agents.forwardlane.com
- Website: https://agents.forwardlane.com
- Canonical page: https://www.zero.xyz/c/agents-forwardlane-com-get-quality-history-ca79de1a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ytup5E121PjRk_NKNjyTW

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-forwardlane-com-get-quality-history-ca79de1a
```

Example prompt: Can you pull the quality score history for the repo 'fx-pricing-engine' over the last 90 days from ForwardLane's platform so I can see how it's been trending?

## When to prefer this

Use this endpoint when you need to understand how code quality has evolved over time for a specific repository, rather than just its current state. It is ideal for due diligence workflows, regression detection, trend analysis, or generating engineering health reports. Prefer this over Get Quality Current when temporal context matters — e.g. you want to see whether quality is improving, stable, or deteriorating.

## Known failure modes

- Unknown or invalid repo name returns empty or error response
- Requested days value outside 1–365 range returns validation error
- Repository exists but has insufficient history for the requested window
- Rate limiting or payment failure may block access
- Sparse or missing data points if repository was inactive during the period

## How this service works

Get quality score history for a repository over N days.

## Output

A JSON object containing the quality score time-series for the specified repository, with data points spanning the requested number of days (default 30, up to 365). Each entry reflects the computed quality score at a point in time, allowing trend analysis and regression detection.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo"
 ],
 "properties": {
  "days": {
   "type": "integer",
   "title": "Days",
   "default": 30,
   "maximum": 365,
   "minimum": 1
  },
  "repo": {
   "type": "string",
   "title": "Repo",
   "description": "Repository name"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "title": "Response Get Quality History Api Quality History Get",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-forwardlane-com-get-quality-history-ca79de1a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.forwardlane.com](https://www.zero.xyz/host/agents.forwardlane.com/llms.txt)