Atlas · getting started
Choose providers from requirements, not recall.
This walkthrough uses the current public Atlas catalog. Follow a requirement through matching, elimination, and evidence—no account required.
Start the comparison01 · State the requirement
Begin with what the work needs.
Atlas selection starts with required capability ids. The agent supplies context and judgment; Atlas supplies the current grounded field.
Example from the current Auth catalog:
02 · Inspect the field
Matches and eliminations are equally important.
A useful selection explains both who remains and exactly which required evidence is absent for everyone else.
1 matches
13 transparent eliminations
Apify
Missing evidence for Multi-factor authentication, Machine-to-machine auth
Auth0
Missing evidence for Machine-to-machine auth
Bright Data
Missing evidence for Multi-factor authentication, Machine-to-machine auth
Browserbase
Missing evidence for Multi-factor authentication, Machine-to-machine auth
03 · Drill into evidence
Verify the claim before judging the trade-off.
Open a matching provider to see each capability tied to the documentation node that supports it. Missing evidence is reported as absence, not silently upgraded into a confident claim. Your agent decides whether that uncertainty is acceptable.
Inspect Kinde's evidence04 · Use it from your agent
The useful result is an evidence-backed decision.
Install the public Atlas skill and connect the shared MFM endpoint. Atlas reads remain anonymous; no workspace is required.