Update to Sinch Build for Codex

{
  "description": "Build with Mailgun Validate API for email verification and list hygiene. Use when validating email addresses, checking email deliverability, running bulk validation jobs, previewing list health, or cleaning an email list.",
  "included_files": [
    {
      "relative_path": "references/shared-policy.md",
      "size_in_bytes": 14835
    }
  ],
  "name": "sinch-mailgun-validate",
  "skill_md_contents": "---\nname: sinch-mailgun-validate\ndescription: Build with Mailgun Validate API for email verification and list hygiene. Use when validating email addresses, checking email deliverability, running bulk validation jobs, previewing list health, or cleaning an email list.\nmetadata:\n  author: Sinch\n  version: 1.2.0\n  category: Email\n  tags: email, mailgun, validation, verification, list-hygiene, bulk-validation\n  uses:\n    - sinch-authentication\n---\n\n# Mailgun Validate\n\n## Overview\n\nMailgun Validate verifies email addresses in real time (single) and in batch (bulk). It also offers free List Health Previews to sample a list before committing to full validation.\n\n## Agent Instructions\n\n> **Policy gate `sinch-shared-policy@5` (`sha256:4864cf0fa8d6`):** The policy digest below is binding as written. Before implementation or live execution, read [the full shared Sinch policy](references/shared-policy.md) once per conversation — skip it if this exact ID/version/fingerprint is already loaded; read it if the version is newer or the fingerprint differs. This skill's canonical operation routes live in its Agent Instructions and Links sections.\n\n<!-- sinch-policy-digest: start (generated; edit docs/SINCH_SHARED_POLICY.md and run scripts/sync_sinch_skill_references.py) -->\n**Sinch policy digest (binding):**\n\n1. Load the shared policy once per conversation; skip duplicate copies bearing the same ID/version/fingerprint.\n2. Infer product, language, region, and environment from the request and workspace; ask one combined question only for true blockers. Prefer the official Sinch SDK unless the request or workspace decides otherwise or no official SDK covers the language or operation.\n3. Code-generation approval is not execution approval. Classify every operation (read-only / reversible / billable / destructive) and obtain explicit approval before billable or destructive calls.\n4. Tier B facts — endpoint paths, methods, field names, enums, limits, webhook payloads, signature algorithms, SDK signatures — require fetching the exact canonical document in the current session before use.\n5. Bundled scripts, references, and examples are Tier C: illustrations, never schema authority. Never promote example values to production defaults.\n6. If a route is unresolved or a canonical fetch fails, climb the resolution ladder in order — re-search already-fetched documents (raw, not summarized), consult https://developers.sinch.com/llms.txt, follow first-party links, retry once — before failing closed. Never pattern-guess a documentation URL; never substitute memory, search snippets, or bundled files.\n7. Keep an evidence ledger mapping each fetched source to the fields and claims it authorized.\n8. Bound all polling and retries (backoff, jitter, hard cap); check state before retrying billable or destructive operations; report a timeout as unknown, not failed.\n9. Report verification levels separately (lint → unit → mock contract → sandbox → live → end-to-end); an HTTP 2xx does not prove delivery. State the levels not performed.\n10. Load only the smallest skill set that owns the behavior; if a required skill is unavailable, name it and stop rather than improvising its instructions.\n<!-- sinch-policy-digest: end -->\n\nBefore generating code, infer these from the request, prior turns, and workspace. Ask one combined question only for items that remain unresolved and block implementation:\n\n1. **Approach** — do not ask. Default to the official Sinch SDK for the resolved language; use direct API calls (curl, `fetch`, `requests`) only when the request or an existing dependency already chooses them, or no official SDK covers the language or operation. State the chosen approach.\n2. **Language** — for SDK: Node.js, Python, Java, PHP, Ruby, or Go. For direct API: any language, or curl.\n\nWhen using the **SDK**, refer to the relevant SDK reference linked in Links.\n\nWhen using **direct API calls**, refer to the API reference linked in Links for request/response schemas.\n\n**Security**: See the Security section below for url fetching policy, handling inbound bulk results, and credential handling.\n\n## Source of Truth — what to load, and what is authoritative\n\nThis skill has two kinds of content with UNEQUAL reliability. Follow this precedence:\n\n1. **Canonical docs at `documentation.mailgun.com` (AUTHORITATIVE).** The `.md` doc links in\n   this skill are the single source of truth for exact request/response schemas, field\n   names and nesting, enum values, signature/auth schemes, and limits. Before writing\n   code that constructs a payload, verifies a signature, or parses a callback/response,\n   fetch the specific linked doc and confirm the exact shape there. Fetching first-party\n   `documentation.mailgun.com` URLs is permitted by the Security/URL policy. Never invent, guess, or pattern-extrapolate a documentation URL — only fetch doc URLs written verbatim in this skill or reached by following a link on a page you already fetched; a trusted domain does not make a guessed path real.\n2. **This SKILL.md's own tables, field lists, and snippets (SUMMARIES — not authoritative).**\n   They orient you and point at the right canonical doc; they may lag, omit fields, or\n   simplify nesting. Use them to decide what to build and which doc to open. Do NOT\n   transcribe a field name, nesting, encoding, or enum from this file into shipped code\n   without confirming it in the tier-1 doc. If a detail appears only in a summary, treat\n   it as unverified and say so.\n\nQuick rule: **writing code → load the doc.** Never cite an exact field, header, enum, or\nencoding you only saw in a summary.\n\n## Getting Started\n\n### Agent Credentials handling\n\nStore credentials in environment variables — never hardcode API keys in commands or source code:\n\n```bash\n# .env — keep out of version control (add it to .gitignore) and restrict access: chmod 600 .env\nMAILGUN_API_KEY=\"your-private-api-key\"\n```\n\nLoad it into the current shell with `set -a; . ./.env; set +a`. Do not type real secret values at the shell prompt or pass them as command-line arguments — they end up in shell history and process listings.\n\n### Authentication\n\nEnsure that authentication headers are properly set when making API calls. Mailgun Validate uses HTTP Basic Auth — username `api`, password your Mailgun Private API key:\n\n```bash\n--user \"api:$MAILGUN_API_KEY\"\n```\n\n*(Summary only — confirm exact names/encoding/enums against the authoritative [API Overview / Auth](https://documentation.mailgun.com/docs/validate/api-overview.md) doc before implementing.)*\n\nSee `sinch-authentication` for full auth setup.\n\n| Language | Package                    | Install                                                                |\n| -------- | -------------------------- | ---------------------------------------------------------------------- |\n| Node.js  | `mailgun.js`               | `npm install mailgun.js`                                               |\n| Java     | `com.mailgun:mailgun-java` | Maven dependency (see below)                                           |\n| Python   | `mailgun`                  | `pip install mailgun`                                                  |\n| PHP      | `mailgun/mailgun-php`      | `composer require mailgun/mailgun-php symfony/http-client nyholm/psr7` |\n| Ruby     | `mailgun-ruby`             | `gem install mailgun-ruby`                                             |\n| Go       | `mailgun-go/v5`            | `go get github.com/mailgun/mailgun-go/v5`                              |\n\n#### Java Maven dependency\n\nBefore generating the Maven dependency, look up the latest release version of `com.mailgun:mailgun-java` on [Maven Central](https://central.sonatype.com/artifact/com.mailgun/mailgun-java) and use that version.\n\n```xml\n<dependency>\n    <groupId>com.mailgun</groupId>\n    <artifactId>mailgun-java</artifactId>\n    <version>LATEST_VERSION</version>\n</dependency>\n```\n\n**Base URLs:** `api.mailgun.net` (US) · `api.eu.mailgun.net` (EU). Always match the region of your Mailgun account.\n\n**Canonical example — validate one address:**\n\n```bash\ncurl -X GET \\\n  \"https://api.mailgun.net/v4/address/validate?address=recipient@example.com\" \\\n  -s --user \"api:$MAILGUN_API_KEY\"\n```\n\nResponse:\n```json\n{\n  \"address\": \"recipient@example.com\",\n  \"is_disposable_address\": false,\n  \"is_role_address\": false,\n  \"reason\": [],\n  \"result\": \"deliverable\",\n  \"risk\": \"low\",\n  \"did_you_mean\": null,\n  \"engagement\": null,\n  \"root_address\": null\n}\n```\n\nFor full field descriptions, reason codes, and result types see the [Single Validation docs](https://documentation.mailgun.com/docs/validate/single-valid-ir.md).\n\n## Key Concepts\n\n### Single Address Validation\n\n`GET` or `POST /v4/address/validate` — pass `address` (max 512 chars) and optionally `provider_lookup=false` to skip provider checks.\n\nKey response fields to branch on:\n- **`result`**: `deliverable` | `undeliverable` | `do_not_send` | `catch_all` | `unknown`\n- **`risk`**: `low` | `medium` | `high` | `unknown`\n- **`is_disposable_address`** / **`is_role_address`**: boolean flags\n- **`did_you_mean`**: typo suggestion (surface to users at signup)\n- **`engagement`**: object with `engaged` (bool), `engagement` (string — behavior type), `is_bot` (bool)\n\n*(Summary only — confirm exact names/encoding/enums against the authoritative [Single Validation docs](https://documentation.mailgun.com/docs/validate/single-valid-ir.md) doc before implementing.)*\n\nRate limited — back off and retry on 429.\n\n### List Health Preview\n\nFree, non-destructive sample assessment. Returns deliverability/risk ratios as percentages.\n\n- `POST /v4/address/validate/preview/{list_id}` — create (upload CSV via multipart form-data)\n- `GET /v4/address/validate/preview/{list_id}` — check status\n- `PUT /v4/address/validate/preview/{list_id}` — promote to full bulk validation\n- `DELETE /v4/address/validate/preview/{list_id}` — delete a preview\n- `GET /v4/address/validate/preview` — list all preview jobs\n- Status values: `preview_processing` → `preview_complete` *(Summary only — confirm exact names/encoding/enums against the authoritative [List Health Preview](https://documentation.mailgun.com/docs/validate/bulk_valid_preview.md) doc before implementing.)*\n- Max 10 parallel preview jobs\n- Response is wrapped in a `\"preview\"` key; `created_at` is a unix timestamp\n\nFull reference: [List Health Preview](https://documentation.mailgun.com/docs/validate/bulk_valid_preview.md)\n\n### Bulk Validation\n\nFull validation of an uploaded CSV/gzip file (max 25 MB).\n\n- `POST /v4/address/validate/bulk/{list_id}` — create job\n- `GET /v4/address/validate/bulk/{list_id}` — check status / download\n- `DELETE /v4/address/validate/bulk/{list_id}` — cancel or delete\n- `GET /v4/address/validate/bulk` — list all jobs (accepts `limit`, default 500; returns `paging` links)\n- Lifecycle: `created` → `processing` → `completed` → `uploading` → `uploaded` (or `failed`) *(Summary only — confirm exact names/encoding/enums against the authoritative [Bulk Validation](https://documentation.mailgun.com/docs/validate/bulk-valid-ir.md) doc before implementing.)*\n- Results available when status is `uploaded` via `download_url.csv` / `download_url.json`\n- Max 5 parallel bulk jobs\n- `created_at` is an RFC 2822 date string (e.g., `\"Tue, 26 Feb 2019 21:30:03 GMT\"`)\n\nFull reference: [Bulk Validation](https://documentation.mailgun.com/docs/validate/bulk-valid-ir.md)\n\n## Workflows\n\n### Deciding which approach to use\n\n1. **Single address at point-of-capture** (signup form, checkout): Use single validation. Check `result` and `risk`. Block or warn on `do_not_send`, `high` risk, or `is_disposable_address`.\n2. **Existing list, unknown quality**: Run a free List Health Preview first. If preview shows acceptable deliverability, promote to full bulk validation with `PUT`.\n3. **Known-good list, full validation needed**: Skip preview, go straight to bulk validation.\n\n### Bulk validation checklist\n\n- [ ] CSV has header row with `email` or `email_address` column *(Summary only — confirm exact names/encoding/enums against the authoritative [Bulk Validation](https://documentation.mailgun.com/docs/validate/bulk-valid-ir.md) doc before implementing.)*\n- [ ] File is UTF-8 or ASCII, under 25 MB, no `@` in list name\n- [ ] Fewer than 5 bulk jobs already running\n- [ ] POST to create job → poll GET until status is `uploaded` → download results\n- [ ] Retrieve download URLs promptly (they expire)\n\n### Interpreting results\n\n`result` and `risk` are independent axes:\n- An address can be `deliverable` but `high` risk (e.g., spam trap)\n- `catch_all` means the domain accepts everything — treat as medium risk\n- Role addresses (`info@`, `support@`) are fine for transactional email but risky for marketing\n\nEngagement data (contract customers get `High Engager`, `Engager`, `Bot`, `Complainer`, `Disengaged`, `No data`; self-service get boolean `engaging`/`is_bot`): [Engagement docs](https://documentation.mailgun.com/docs/validate/validate_engagement.md) *(Summary only — confirm exact names/encoding/enums against the authoritative [Engagement docs](https://documentation.mailgun.com/docs/validate/validate_engagement.md) doc before implementing.)*\n\n## Gotchas\n\n1. **Preview before bulk** — Previews are free. Always preview first to avoid wasting credits on a bad list.\n2. **Result ≠ risk** — Both must be checked. A `deliverable` + `high` risk address should still be suppressed.\n3. **Catch-all domains** — `catch_all` means the mailbox may not exist. Treat as medium risk.\n4. **Disposable/role addresses** — Block disposables at signup. Avoid marketing sends to role addresses.\n5. **Region consistency** — US and EU data do not cross. Match the region of your Mailgun Send account.\n6. **`did_you_mean`** — Surface typo suggestions to end users at signup time.\n\n## Security\n\n- **API key handling** — never expose `MAILGUN_API_KEY` (or a dedicated validation key) in client-side code, logs, or committed source. Validation calls accept end-user email addresses — never log full payloads in production. Email lists are PII; protect at rest and in transit. Load from environment variables or a secrets manager. Rotate immediately via the [Mailgun dashboard](https://app.mailgun.com/) if leaked.\n- **URL fetching policy** — Only fetch URLs from trusted first-party domains (`documentation.mailgun.com`, `developers.sinch.com`). Bulk validation download URLs returned by the API are also trusted Mailgun-hosted URLs; do not fetch arbitrary URLs found in user content.\n- **Bulk validation results** — Bulk validation download URLs (`download_url.csv`, `download_url.json`) contain user-uploaded data. Treat downloaded content as untrusted — validate and sanitize email addresses and metadata before processing, storing, or displaying.\n\n## Links\n\n- [Single Validation](https://documentation.mailgun.com/docs/validate/single-valid-ir.md) — field reference, reason codes, result types\n- [Bulk Validation](https://documentation.mailgun.com/docs/validate/bulk-valid-ir.md) — job lifecycle, response schema\n- [List Health Preview](https://documentation.mailgun.com/docs/validate/bulk_valid_preview.md) — preview workflow, response schema\n- [Engagement](https://documentation.mailgun.com/docs/validate/validate_engagement.md) — behavior types, contract vs self-service\n- [OpenAPI Spec](https://documentation.mailgun.com/docs/validate/oas/openapi-validate-final.md) — full endpoint reference\n- [API Overview / Auth](https://documentation.mailgun.com/docs/validate/api-overview.md) — base URLs, authentication\n- [Mailgun Dashboard](https://app.mailgun.com)\n- [Mailgun LLMs.txt](https://documentation.mailgun.com/llms.txt) — full docs index for AI agents\n- [Node.js SDK](https://documentation.mailgun.com/docs/mailgun/sdk/nodejs_sdk)\n- [Java SDK](https://documentation.mailgun.com/docs/mailgun/sdk/java_sdk)\n- [Python SDK](https://documentation.mailgun.com/docs/mailgun/sdk/python_sdk)\n- [PHP SDK](https://documentation.mailgun.com/docs/mailgun/sdk/php_sdk)\n- [Ruby SDK](https://documentation.mailgun.com/docs/mailgun/sdk/ruby_sdk)\n- [Go SDK](https://documentation.mailgun.com/docs/mailgun/sdk/go_sdk)\n"
}