set_profile

org.lexlint/lexlint · Verify this server

Step 1 of the lint. Declare what the app does (activities) and where it will operate (jurisdiction slugs); get back the validated, canonical profile plus what the corpus holds for each jurisdiction, so the depth of a run is known before it is spent. Write the returned profile into the project's lexlint.yml and pass it to run_lint. Stores nothing server-side. An unknown activity or a malformed slug is refused here rather than silently weakening a lint later. Costs one upstream request for any number of jurisdictions. It answers the same coverage question check_access's own jurisdictions preview does, off a request check_access spends either way, so asking both is redundant, never costlier: they just repeat the same answer. Requires X-API-Key (an UnGovr Open Data key, passed through and metered upstream; get one at https://ungovr.org/settings/api-keys?cli=lexlint).