# GitHub on looot

GitHub gives your agent 2 jobs through looot: get developer zen, get a GitHub repository. 2 endpoints run today, some of them free.

## At a glance

- Category: Developer data
- Access: No key needed: these endpoints are open, looot calls them for you
- Price: some free

## Choose it when

- You need to get developer zen: GitHub is the only provider on looot that runs this job today.
- You need to get a GitHub repository: GitHub is the only provider on looot that runs this job today.
- You want to start without any key: some of its endpoints are open and looot calls them for you.

## Endpoints and jobs

| Endpoint | Job | Price | Runs (30 days) | Benchmark |
|---|---|---|---|---|
| [zen](/public-catalog/github-zen) | `developer.zen.get` | free | 85.7% of 14 runs without an error, median 220 ms | no benchmark yet |
| [Get repository details](/public-catalog/github-repo-get) | `github.repo.get` | $0.0001 per call | not enough runs to rank | no benchmark yet |

## How the numbers are measured

Run numbers are looot's own runs of each endpoint over the last 30 days: the share that completed without an error, and the median time to answer. An endpoint with fewer than 10 runs in that window shows "not enough runs to rank" and is never ranked. Prices are what looot charges per call or per result, fee included, read from the live catalog; you prepay credit and each call is charged when it runs.

Read 2026-11-10 23:22 UTC.

## For agents

The minimal request for zen (`github-zen`). Replace each <placeholder> with your value and send a new idempotency key per run.

### MCP

```json
{
  "endpointId": "github-zen",
  "input": {},
  "idempotencyKey": "<a new id per run>"
}
```

### REST

```bash
curl -X POST https://api.looot.ai/v1/runs \
  -H "Authorization: Bearer $LOOOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endpointId":"github-zen","input":{},"idempotencyKey":"<a new id per run>"}'
```

### CLI

```bash
looot run github-zen --input '{}'
```