eurodns
EuroDNS records
Resolve RU/EN prose into mode, domain, and record selection; never use the first word as the domain.
| Mode | EN keywords | RU keywords |
|---|---|---|
show (default) |
show, list, view, get records, check | покажи, список, посмотри, проверь |
add |
add, create, new record | добавь, создай, новая запись |
update |
update, change, modify, edit, redirect | обнови, измени, поменяй, настрой редирект |
delete |
delete, remove, drop | удали, убери, сними |
Strip flags; one explicit mode token wins. Otherwise score distinct whole-word keyword hits: unique highest wins; a tie involving delete needs clarification; a tie with show resolves to show; add/update ties use the earliest keyword. Conflicting explicit modes need clarification. Zero matches or empty input resolves to show. Ask for a missing domain or outcome-changing ambiguity before API work; clarify deletion scope before target inspection if necessary. Use available Codex input tools for optional questions; required approval needs an explicit user response, never a timeout or absent tool result.
Before the first API call emit one English PLAN — eurodns block with INPUT, MODE, SCOPE (domain and record identities), DO, and RESULT. Redact credentials if present in user input.
Provider contract and credentials
Verify API routes, status codes, auth header names, IP restrictions, and schemas against provider OpenAPI and official documentation before a future API operation. Do not invent endpoints when verification fails.