Find collaborators whose GitHub proves the skill.
Name what you need. Plaza ranks builders on evidence measured from their public repositories — and shows you the repos behind every match.
Arithmetic you can check, not a score we invented.
- 01
Read the account
Public repositories only: languages measured in bytes, repo topics, stars on their own work, and how recently each repo was pushed. Nothing self-reported.
- 02
Score it deterministically
0.85 × skill-evidence coverage + 0.15 × trust scoreTrust is five documented GitHub components out of 100. No LLM, no embeddings: the same account and the same query always produce the same number.
- 03
Show the working
Every match cites the repositories behind it. Where a skill has no evidence, Plaza names the gap instead of guessing — and a candidate with zero measured evidence is never returned at all.
What’s live, and what isn’t.
- Evidence matching — search any skills, free, no sign-in needed
- Builder profiles with the measured evidence behind each one
- Collaboration requests — ask once, they accept or decline, and only then can you talk
- Sign in with GitHub to index your own account
- Council — the multi-agent game, free with guest play
- The same data over the API:
GET /api/discover
- LinkedIn as a second identity source
- Request Market for posting what you need
- Availability and intent you state yourself
- Project Cards
This is the whole list. Nothing above is described anywhere on this site as if it already worked.
Turn a document into a table of scheming AI characters.
The playable side of polyagent: upload a PDF or paste text and enter the game as a guest. Free, no sign-up.
Open Council →Get told when the rest ships.
Matching, profiles and collaboration requests are already open — you do not need this to use Plaza. Leave an email and we will write once, when the flows above move from “not built yet” to live.
What does Plaza actually measure about a builder?
Only public GitHub evidence, read through the REST API: languages counted in bytes, when each repo was last pushed, repos owned, followers and stars. Nothing is self-reported and no model invents a number — these are constants in the code.
- Skill strength
- 50% recency · 30% measured volume · 20% breadthThe three terms behind one skill's strength (app/lib/match.ts).
- Self-declared topics
- kept at 60% strengthA repo topic the owner typed is weaker evidence than bytes we counted, so it is discounted rather than trusted.
- Final ranking
- 85% skill coverage + 15% Trust ScoreCoverage dominates on purpose: the question is whether they can do this, not whether they are famous.
- Trust Score, out of 100
- code depth 28% · repos owned 18% · recency 15% · cadence 12% · account age 12% · stars 8% · followers 7%Seven components (app/lib/github-evidence.ts). Followers and stars — the two numbers you can accumulate without writing code — are worth 15% together.
- Recency half-life
- 60 daysNot a yes/no 'active' badge: someone who pushed yesterday reads differently from someone who pushed on day 89.
- Cadence window
- 90 days, saturating at 30 reposHow much ground an account covered recently, counted from push dates.
- Repos-owned band
- 1 repo to 100 reposLog-scaled between a floor that says nothing and a knee only the top of the real population reaches.
- Account-age band
- 6 months to 15 yearsMeasured from the GitHub account's own creation date, never self-reported.
- Language bytes read
- the 8 repos pushed most recentlyGitHub allows 60 unauthenticated REST requests in 1 hour, so byte-level detail is spent on the freshest work first.
- Cost to search
- US$0, no accountSigning in with GitHub is also free; it indexes your own public activity so others can find you.
- Contact limit
- 5 outgoing requests per 24 hoursA per-person cap, so nobody can be volume-mailed through Plaza.
- Sign-in session
- 30 daysA signed cookie, refreshed on sign-in. Plaza stores no password of yours at all.
How do you check that a developer really wrote what they claim?
Five things people actually do, and what each one can and cannot establish. Reading a CV proves nothing checkable; an interview measures interview performance; public code proves authorship but only of public code.
| Method | What it actually proves | Typical time | Cost | Where it fails |
|---|---|---|---|---|
| A CV or résumé | Nothing checkable — every line is written by the candidate | 1–2 minutes to read | US$0 | No claim on it points at an artifact you can open |
| Reading their GitHub by hand | Authorship of public repos, if you open each one | 10–20 minutes per person | US$0 | Does not scale past a shortlist; forks and starred repos read like their own work |
| A technical interview | How they solve one fresh problem while watched | 45–60 minutes, two people | 1–2 hours of engineering time | Measures interview performance, not what they have shipped |
| A take-home exercise | New code they wrote for your prompt | 4–8 hours of theirs, 30 minutes of yours | Unpaid work, or a real fee | High dropout, and it still says nothing about their past work |
| Plaza's measurement | Bytes of each language in their public repos, push dates and stars — with every repo cited | Under 1 minute | US$0 | Blind to private and company-internal work, which is most work |
Only the last row is measured by Plaza. The times and costs on the other four are typical industry practice, stated as ranges — we did not measure them, and the table says so rather than dressing an estimate up as a finding.
Where can you verify all of this yourself?
Every input Plaza reads is a documented, public GitHub endpoint, and every figure above is a constant in open code. These are the first-party specs — not commentary about them.
- GitHub REST API — Repositories — the endpoint every repo, star count and push date on Plaza is read from
- GitHub REST API — Users — account age, public repo count and followers, the three account-level trust inputs
- GitHub REST API — rate limits — why an ingest reads language bytes for 8 repos and not for all of them
- GitHub's own OpenAPI description — the machine-readable contract for the responses above, published by GitHub
- api.github.com/rate_limit — live — open it and GitHub itself returns the 60-per-hour figure quoted above
- git log — Git reference manual — the same authorship record, readable offline once you have cloned the repo
- Open Source Guides — how to contribute — what public contribution history does and does not say about a person
Before you search.
What is Plaza?
Plaza is a trust layer for finding collaborators. It reads a builder’s public GitHub activity — repository languages measured in bytes, repo topics, stars and push dates — and turns it into one structured signal you can audit, so you can judge whether a potential collaborator is credible for the skill you actually need before you reach out.
How does Plaza verify that a builder is credible?
Credibility comes from measured public GitHub activity, not self-declared claims: a Trust Score built from five documented components — account age, public repositories, followers, repositories pushed in the last 90 days, and stars on the account’s own work — each reported so any displayed number can be checked. Signing in with LinkedIn is not built yet; when it is, this page will say so.
How does matching work?
Matching is deterministic, not generative. For each skill you ask for, Plaza measures how strongly a builder’s public repositories evidence it — recency, volume of code, and how many repositories carry it — and ranks by 0.85 × skill-evidence coverage + 0.15 × trust score. Every result shows that arithmetic and links the repositories it cites, and a builder with no measured evidence for your skills is never returned.
Will Plaza spam my inbox?
No. Contact is one structured request at a time: someone tells you why they are reaching out and writes a short pitch, and nothing more reaches you unless you accept. Plaza exposes no contact details — it holds no email address for you — and caps how many requests one person can send in a day.
How much does Plaza cost, and when can I use it?
Matching is live now and free: open Plaza and search without an account. Signing in with GitHub is free too, and indexes your own public activity so others can find you.