Docs menu
Get started
Quickstart Install: Claude Code Install: Codex Install: Kiro Install: other clients API keysConcepts
How a run works The app profile The severity model What a run does not sayTools
check_access claim_trial_key set_profile run_lint get_law resolve_domain_jurisdiction submit_feedback upload_lint_runGuides
A whole run, end to end Console TestPack in CIReference
Endpoint and transport lexlint.yml schema Errors ChangelogHelp
Support and feedbackTools
set_profile
Declare what the app does and where it operates. Nothing is stored.
What it does
Step 1 of the lint. Declare what the app does and where it operates; get back the validated,
canonical profile plus what the LexLint law library holds for each jurisdiction, so you know the depth
of a run before spending it. Write the returned profile into the project's
lexlint.yml and pass it to run_lint. It takes the same declaration as
run_lint, and the table below lists each parameter.
It stores nothing. mcp.lexlint.io has no session, and splitting the lint in two did not give it one: the profile lives in your repository, not here. An unknown activity or a malformed slug is refused at this step rather than quietly weakening a lint later, and a malformed slug is refused outright, by name, before any request is spent. A profile that lints clean over fewer jurisdictions than you declared is worse than an error, so this step will not hand you one.
It costs one upstream request for any number of jurisdictions. That is a separate
request from check_access's own, but it answers the same coverage question, so
asking both gets you that answer twice for the two calls a normal run already makes, not for
a third one. If you are calling check_access a second time later, for example to
revalidate a local cache, ask it or set_profile for coverage, never
both, since a second check_access call really is a second request.
Parameters
| Name | Type | Required | What it takes |
|---|---|---|---|
activities | string[] | yes | What the app does. Allowed: crawls_web, trains_models, generates_content, deploys_chatbot, deploys_companion_chatbot, deploys_mental_health_chatbot, automated_outreach, places_automated_calls, sends_automated_texts, sends_commercial_email, sends_faxes, high_risk_decisions, processes_voice, processes_biometrics, processes_personal_data, processes_deidentified_data, publishes_adult_content, operates_social_platform, serves_minors, operates_app_store, ships_mobile_app, ships_consumer_interface, relies_on_digital_identity, collects_e_signatures, ships_encryption, serves_sanctioned_destination, aggregates_content, distributes_software_product, handles_health_records, provides_financial_services, operates_essential_service, is_listed_company, provides_telecom_services, provides_cloud_services, provides_general_purpose_ai_model, is_frontier_developer, serves_education_institutions, serves_k12_schools, serves_higher_education, statutory_requests, records_calls, records_text_chat, tracks_devices, is_bank, is_lender, is_insurer, is_securities_firm, is_payment_provider, is_crypto_asset_provider, employment_decisions, credit_decisions, insurance_decisions, housing_decisions, education_decisions, health_care_decisions, public_services_decisions, justice_decisions, generates_text, generates_images, generates_video, generates_audio |
activities_left_out | string[] | no | Activities the developer was asked about and said this software does not do. Today it answers processes_personal_data: unsent, a declaration naming any activity its code settles is matched as if it processes personal data, with an info coverage line, until the developer answers. It also answers the two chatbot kinds: deploys_chatbot with neither declared nor left out is matched as if it is both, with an info coverage line. And it answers the two model-provider roles: trains_models with a role neither declared nor left out is asked about it, with an info coverage line counting the laws that bind it. Left out, serves_education_institutions says no school, college or university runs or buys this software, so serves_minors no longer brings school law in. And it answers the eight decision domains: high_risk_decisions does not reach a domain left out, so a decision that fits none, such as fraud screening, leaves all eight out. |
jurisdictions | string[] | yes | Jurisdiction slugs, lowercase, "/"-separated (e.g. "us", "us/ca", "eu", "kr"). A slug is the jurisdiction's UnGovr Atlas path: California is https://ungovr.org/us/ca and its Atlas ID is urn:ungovr:us/ca. Its ISO 3166 code, US-CA, is accepted too. A deeper or unresearched path resolves to the nearest jurisdiction whose law reaches it, and to none for a place with its own legal system, and the jurisdictions whose law is researched are listed at https://lexlint.io/law for the developer to check; name every jurisdiction the app operates in: one left off is unlinted, not passed. |
public_sector | string[] | no | Is this software run by a public body (body), sold to or run for public bodies (supplier), both, or neither (none)? Ask the developer every time the profile is declared; never infer it from the code. Omitted, duties binding only public bodies are reported as the caller's, and run_lint counts them in a coverage line. body: A public body runs this software. supplier: You sell this software to public bodies or run it for them. |
public_sector_functions | string[] | no | Which kinds of public body run or buy this software. Ask only when public_sector is body or supplier, and never infer it from the code. One or more of: general (a general-purpose public body, such as a city hall, a state department or a federal agency), law_enforcement (police and sheriffs), corrections (prisons, jails, parole and probation), prosecution_courts (courts, prosecutors and public defenders), public_education (public schools, school districts and public universities), public_health (health departments and public hospitals), elections (election offices), public_benefits (agencies deciding welfare, unemployment or Medicaid eligibility), emergency_services (911 centers, fire and emergency medical services). A duty that binds only another kind is reported as someone else's; a duty that binds every public body always reaches you. Omitted, every public-body duty reaches you, and run_lint counts the ones that bind a single kind in a coverage line. |
regulated_sector | object | no | Whose duty a financial-law row is. Is this software run by a bank, insurer or other regulated financial entity (body), supplied to one (supplier), or neither (none)? {"financial": "supplier"}. Ask when provides_financial_services or a license class (is_bank, is_lender, is_insurer, is_securities_firm, is_payment_provider, is_crypto_asset_provider) is declared; never infer it. It routes and never matches, so a supplier still declares the classes of its customers. Omitted, the entity's duties are reported as the caller's, and run_lint counts them in a coverage line. For education: is this software run by a school, district, college or university, public or private (body), supplied to one (supplier), or neither (none)? {"education": "supplier"}. Ask when serves_education_institutions, serves_k12_schools or serves_higher_education is declared. Omitted, public_sector body or supplier with public_sector_functions naming public_education answers it. |
roles | object | no | Which role this software's maker holds, keyed by axis: ai_system (provider, deployer, importer, distributor, product_manufacturer, authorised_representative) and personal_data (controller, processor). Each is the position under each regime's own law, whatever it calls it, such as Colorado's developer (provider), or the CCPA's business or India's data fiduciary (controller). {"ai_system": ["provider"], "personal_data": ["processor"]}; "none" alone when asked and no regime gives it one. Ask the developer; never infer it from the code. Omitted, an axis routes nothing and run_lint counts the duties a role would move in a coverage line. |
flows | object[] | no | Where this software stores or sends personal data across a border, one entry per route: [{"from": "eu", "to": "us", "data": "personal", "basis": "contract_clauses"}]. from and to are jurisdiction slugs, as jurisdictions takes them; data is personal or sensitive; basis is the transfer mechanism the route relies on: adequacy, contract_clauses, binding_rules, certification, authority_approval, consent, derogation, unknown. [] when asked and no personal data leaves the jurisdiction it was collected in. Ask the developer; never infer it from the code. Each cross-border transfer finding then names the declared flows that leave its jurisdiction. No finding is dropped or downgraded on a flow. |
derived | boolean | no | true adds derived findings: the records an app holds to meet the deadlines the matched laws set, inferred by LexLint and traced to each law. false leaves them out; omitted, the server default applies. |