--- name: rn description: Apply an organization's personal-data policy before compatible model inference. Evaluate the protected route and selected model before using metered credit. --- # Rota Nacional MCP tools: `listar_modelos`, `pricing`, `limpar_dados_pessoais`, `conversar`, `native_mistral_ocr`, `consultar_recibos_inferencia`. Use the organization's protected route instead of adding policy and usage billing to every compatible client. ## Everyday requests Use this skill for model choice, authorized inference, personal-data processing and payment recovery. Reuse the approved organization, model, connection and spending authority. Ask for missing input or access. Preserve privacy policy and external-routing consent. Return useful output and evidence. Do not infer authority to disable controls or repeat a charge. - "Which models are available for text summaries and what does each option cost?" Read `listar_modelos` and current pricing. - "Remove personal data from this text before I share it." Check the quote and use `limpar_dados_pessoais`; do not promise perfect detection. - "Summarize this text using my organization's privacy policy." Use `conversar` with the approved model and protected contract. - "Extract this PDF's text and preserve page references for review." Verify the authorized Mistral connection and quote before `native_mistral_ocr`; the native gateway has no content barrier. - "My last AI request failed. Check whether it was charged before retrying." Read `consultar_recibos_inferencia` before any new inference. ## Choose and evaluate Read `https://rota-nacional.ia.br/v1/models` and the current trial terms. Use `POST /v1/chat/completions` for the documented protected chat contract. Evaluate the policy with permitted test data before sending real data. Keep the organization's approved provider, model and route. External routing needs the organization's consent. The native provider gateway is a different contract and does not apply the content barrier. Privacy controls do not guarantee detection of every personal datum or inference inside Brazil. If the required provider contract is unsupported, do not invent an adapter or use a direct fallback. ## Security boundary Provider credentials are kept in envelopes encrypted by a key-management service (KMS) inside a measured Nitro vault. The cryptographic context binds product, organization, record, provider and destination. The app uses a capability with no operation to export the secret. Core TLS (transport security) uses AWS Certificate Manager (ACM) certificates integrated with Nitro Enclaves and the PKCS#11 interface; export is disabled. Persistent storage uses LUKS encryption and opens only through the owner's manual procedure. The edge, app and host still process content. This protection does not promise complete security, that all memory is locked, data residency in Brazil, an SLA or a certified audit. A critical failure closes admission and requires a new manual opening. Encrypted database and envelope backups were verified. Configuration copies are static; there is no automatic copy job yet. The security alert and external monitor are separate. In the core zone, DNSSEC is validated and CAA restricts certificate issuance to Amazon. Customer domains have their own DNS and certificate configuration. Credit pays for metered use. Compare input and output rates for the selected model. The trial is not unlimited production capacity. For OCR, audio or other capabilities, read their separate quote and job contract. Contracts: [task index](https://rota-nacional.ia.br/llms.txt). ## Connect and pay Use existing tools, the approved HTTP endpoint or `https://rota-nacional.ia.br/mcp`. Read [prices](https://rota-nacional.ia.br/api/pricing) and [payment](https://rota-nacional.ia.br/api/billing). Reuse existing access and spending authority. Keep organization and credit credentials secret. Use account-free payment only on an operation that explicitly offers it. On direct MCP, an authorized x402 retry uses `params._meta["x402/payment"]`. An authenticated MCP connection already supplies access. Do not request another key or credit code. For shared account API calls, use `X-Api-Key: mmk_…` or `Authorization: Bearer mmo_…` (OAuth). On paid operations that accept account balance, that credential also authorizes payment. HTTP x402 uses `PAYMENT-SIGNATURE`; account-free credit uses `Authorization: Bearer cred_…`. Keep the documented idempotency identifier and recover uncertain payment or job state before paying again. In `checkout=site`, the person purchases on the site. ChatGPT uses existing rights without sales.