# Repository Pulse – Agent Evidence Utilities

> Repository Pulse – Agent Evidence Utilities is a paid API for AI agents from dependency-truth.inboxtzdjqv.workers.dev, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-02).

Returns deterministic repository health metadata for a given GitHub owner/repo pair, including latest commit, release, open issues, archive status, and default branch.

## Facts

- Endpoint: POST https://dependency-truth.inboxtzdjqv.workers.dev/v1/repo-pulse?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/repository-pulse-agent-evidence-utilities-dfe0ed97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p2vBrlkbT5AQUjL8bXrs6

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 repository-pulse-agent-evidence-utilities-dfe0ed97 -d '<json body>'
```

Example prompt: Can you check the repo pulse for markedjs/marked — I want to know if it's still active, what the latest release is, how many open issues it has, and whether it's been archived?

## When to prefer this

Choose this endpoint when you need deterministic, citable repository health data — specifically archived status, open issue count, latest commit, and latest release — for a known GitHub owner/repo pair. Prefer it over scraping GitHub directly when you need a structured, pay-per-call API that is safe for agent pipelines. It complements the sibling npm/PyPI version-check endpoint when you want both package and repo-level evidence.

## Known failure modes

- Invalid or non-existent owner/repo returns an error or empty response
- Private repositories that are inaccessible return authorization errors
- Rate limiting on the underlying GitHub data source may cause transient failures
- Repositories with no releases will have a null or absent latestRelease field
- Malformed input (missing owner or repo field) returns a validation error

## How this service works

Deterministic package, repository, security, and citation evidence APIs payable per call with x402.

## Output

A JSON object containing the repository's full name, archived boolean, open issue count, default branch, latest commit SHA, latest release tag, and an array of provenance URLs — all deterministically fetched and suitable for agent reasoning or citation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "repo": {
   "type": "string"
  },
  "owner": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "archived": false,
  "openIssues": 100,
  "repository": "markedjs/marked",
  "latestCommit": {
   "sha": "abc123"
  },
  "defaultBranch": "master",
  "latestRelease": {
   "tag": "v16.3.0"
  },
  "provenanceUrls": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/repository-pulse-agent-evidence-utilities-dfe0ed97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dependency-truth.inboxtzdjqv.workers.dev](https://www.zero.xyz/host/dependency-truth.inboxtzdjqv.workers.dev/llms.txt)