Records API
Your fighters, with a verified record and a suspension read, in an afternoon
Pansofica verified records API, by PXL8 Technology, Inc.
Matchmaking runs on trust: is this the fighter they say they are, what is actually on their record, and is there anything on file that stops the bout. Today that is a phone call, a screenshot and a guess. This API answers all three from the commissions’ own published documents, in one request each.
This is the first API on the engine, in combat sports, where the engine runs in production today. Another register means another schema, not another API.
What you get
- 01
Resolve once, read forever.
Send a name and the anchors you hold: hometown, division, discipline. You get a short list of candidates, each with a confidence band and the anchors that matched, plus our id. Store the id; every later read is by id.
- 02
The verified record, labeled.
Every bout we hold for that fighter, read from the athletic commission’s or federation’s own results document: date, opponent, result, method, round, the commission that published it, and the document itself (URL and hash) so you can show your users where the line came from. The tally is labeled with the date our file begins. It counts what the named commissions published, and it is never padded with anything we did not read from a document.
- 03
The suspension read.
What our sources say about the fighter right now: every suspension printed against them (until when, by which commission, on which document, read when), their last bout and how long ago, whether a recent stoppage loss is on file, and which commissions we cover for them with the dates covered. It tells you what is published, so your matchmaker can confirm with the supervising commission in one call instead of three.
- 04
Tell us the bout, get the link-back.
Post a made bout as soon as you make it: date, corners, discipline, status. It is held as your record, separate from the verified one. When the commission publishes the result sheet, we link your submission to the verified bout and report how many days ahead you were.
GET {BASE_URL}/partner/v1/fighters/search?name=&hometown=GET {BASE_URL}/partner/v1/fighters/:idGET {BASE_URL}/partner/v1/fighters/:id/clearancePOST {BASE_URL}/partner/v1/boutsThe suspension read comes back as one of three states
Facts, not advice. Each state carries the documents behind it and the commissions covered.
- State 1
a suspension on file
- State 2
no suspension on file
- State 3
insufficient coverage for the region you asked about
Why it is different
- Source, not scrape. Every verified line traces to a document published by the commission or federation that supervised the bout. No record keepers, no crowd-sourced tables.
- One record per fighter across commissions. A fighter licensed in two states has one id and one record with us.
- Never a padded number. Where our coverage begins is on the response. A count is a count.
- A machine-readable suspension state. One of three states on every read, with the documents behind it.
- Ask it from an assistant. The same record answers an AI assistant through a Model Context Protocol server, with the canonical page to cite.
Integrating
- JSON over HTTPS, one bearer key per environment. A sandbox key reads a frozen set of real fighters, so your integration is built without touching a live quota.
- Three reads and one write. Small cursor pages. No bulk export, by design.
- Rate limits and a monthly quota per key, both visible on a usage route and on every response’s headers.
- A one-page README with copy-paste examples, and an OpenAPI 3 document for your client generator.
What it is not
It is not a medical or regulatory clearance, and it does not replace the supervising commission. Absence of a suspension in our sources is not proof that none exists. It is a fast, honest read of what the commissions have published.
Data as published by the named athletic commissions and federations. Terms on request.
Tell us which fighters you need to check.
We reply by email, from a person who can answer questions about coverage.