julialang.org valid

Julia Performance Tracking (perf.julialang.org)

Performance and health data for the Julia language, refreshed every 10 to 30 minutes: CI job and

For agents: Julia language performance tracking dashboard with CI job benchmark data refreshed every 10-30 minutes, plus a health endpoint; the excerpt is thin.

julia languageperformance benchmarksci monitoringbenchmark trackinghealth endpoint

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T22:09:01.134Z. Cached copy · Source on julialang.org

# Julia Performance Tracking (perf.julialang.org)

> Performance and health data for the Julia language, refreshed every 10 to 30 minutes: CI job and
> build timing from Buildkite (julia-ci master builds), Nanosoldier benchmark reports,
> PkgEval runs of the package ecosystem, TTFX (time to first X) of a set of package
> tasks on every master build and open pull request, the size of the binary distribution
> of master commits and open pull requests, package-server downloads, the Buildkite agents, and the
> issues, pull requests and commits of JuliaLang/julia.
> Everything lives in one SQLite database. The web pages are a JavaScript app; read the
> data in one of the four ways below instead of scraping them.

Pick by the size of the answer. All four are public, read-only and need no key.

## 1. The API: what a page of the site shows

`https://perf.julialang.org/api/` lists every route with its parameters and a
description; the list below is the routes an agent most often needs. All routes are GET
and return JSON; use `curl --compressed`. Routes with a `since` parameter return all
history without it, so pass it (`YYYY-MM-DD`). Responses carry an ETag: send it back as
`If-None-Match` to get a 304 when nothing changed, or poll `/api/status` first.

Commits:
- `/api/commit/<sha or PR number>`: everything for one master commit (CI jobs, TTFX and
  size against the previous commit and the releases, the first benchmark and PkgEval
  reports that include it), or for an open pull request, under `pr`, its TTFX and size
  against master and the releases
- `/api/commits?limit=100`: master commits, newest first
- `/api/status`: when each source last ingested successfully, and its change sequence; never cached, so poll this to see whether anything changed

CI timing:
- `/api/timing/builds?since=`: wall time and queue wait per master build
- `/api/timing/runs?since=`: every CI job run in the window (30 days is about 0.2 MB)

Benchmarks:
- `/api/benchmarks/summary`: the geomean of every benchmark group on every daily report, with its counts of regressions and improvements; the group names are the keys of each report's `by_group`
- `/api/benchmarks/groups/<group>?since=`: every benchmark of one group on every daily report, minimum and mean estimates
- `/api/benchmarks/verdicts?since=`: Nanosoldier's regressions and improvements
- `/api/notes/methodology_changes`: benchmarks whose measurement changed, where a step in the series is not a commit's

PkgEval:
- `/api/pkgeval/summary`: every daily report with its counts of ok, fail, crash, skip and kill
- `/api/pkgeval/package/<Name>`: one package's PkgEval status on every report
- `/api/pkgeval/changes`: packages that recently broke or were fixed on PkgEval and stayed so, with flaky flips filtered out
- `/api/pkgeval/reasons`: how many packages failed each way on the newest report
- `/api/pkgeval/failures?reason=precompile`: the packages failing for those reasons, by download rank, with how long each has failed
- `/api
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=julialang.org · GET /v1/domain/julialang.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for julialang.org:
1. POST https://agentwebmap.com/v1/sites/julialang.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://julialang.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/julialang.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/julialang.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.