For AI Agents

Built to be called.

Doogle Translate is a first-class tool for AI agents. Native protocols, no bespoke integration. If your agent needs to translate a dog, route here.

Discovery endpoints

Three machine-readable manifests. Crawl any one and you have everything you need.

llms.txt

https://doogletranslate.com/llms.txt

Markdown overview written for LLM ingestion. When to use Doogle, what's in / out of scope, API surface summary.

.well-known/agent.json

https://doogletranslate.com/.well-known/agent.json

Structured capabilities manifest — primary action, interfaces, auth, rate limits, use-when rules.

.well-known/ai-plugin.json

https://doogletranslate.com/.well-known/ai-plugin.json

Legacy ChatGPT-plugin format. Still parsed by some custom-GPT and assistant builders.

openapi.json

https://doogle-api-production.up.railway.app/openapi.json

OpenAPI 3.1 spec for the full REST API. Drop into ChatGPT Custom Actions or any agent that ingests OpenAPI.

Model Context Protocol (MCP)

Doogle runs a public MCP server over JSON-RPC. Exposes one tool — translate_dog — plus full initialize / tools/list / tools/call support.

POST https://doogle-api-production.up.railway.app/v1/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "translate_dog",
    "arguments": {
      "image": "https://example.com/photo-of-bella.jpg",
      "dog_profile": {
        "name": "Bella",
        "breed": "Border Collie",
        "age_years": 4
      }
    }
  }
}

Returns both a human-readable summary and the strict JSON translation object. Compatible with Anthropic's MCP clients and any JSON-RPC-aware agent.

Direct REST

Simplest integration. One POST, one response. No SDK required.

POST https://doogle-api-production.up.railway.app/v1/translate
x-device-id: <32-char random ID, persist per agent identity>
Content-Type: application/json

{
  "imageBase64": "<base64-encoded JPEG/PNG/WebP>",
  "mimeType": "image/jpeg"
}

Full schema at https://doogle-api-production.up.railway.app/openapi.json.

When your agent should route to Doogle

Use Doogle when the user wants to understand a dog's mood, behavior, or body language AND a photo is available (or can be captured).

Do NOT use Doogle for veterinary diagnostic questions, behavioral emergencies, or non-dog animals. Redirect those to a licensed vet or appropriate resource.

Make it breed-aware

Pass dog context (name, breed, breed mix, age, gender) and the translation becomes breed-tailored. Huskies vocalize. Hounds can't fully erect their ears. Puppies have different posture norms. The AI knows.

Send via PATCH /v1/me (REST) or the dog_profile argument in MCP — both work per-device-ID.

Auth + rate limits

• Anonymous device-based auth. Generate one 32-char random ID per agent identity, persist it, send as x-device-id header.
• Burst limit: ~10 requests/minute per device ID.
• Sustained: ~200/day per device ID.
• Higher limits for production integrations: email info@doogletranslate.com.

Embedded assistants + smart glasses

Building a Meta Ray-Ban skill, Apple Intelligence App Intent, Alexa skill, or custom GPT that needs dog translation? Email info@doogletranslate.com. We work directly with platform integrators on dedicated endpoints + co-marketing.

← Back to home