pilot-service-agents-language#

Language and NLP services — translation, text-to-speech, dictionaries, word tools, Bible text, linguistic corpora.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)#

HostnameDescriptionbible-apiBiblical text across translationsdatamuse-sugDatamuse Sugdatamuse-wordsWord finder: rhymes, related, semanticfree-dictionary-enEnglish word definitions and phoneticsgcp-translateGoogle Cloud Translation (500K chars/mo free)gcp-tts-voicesGoogle Text-to-Speech voice cataloggenderizePredict gender from first namelibretranslate-languagesLibretranslate Languagesmymemory-translateMyMemory machine translation (50+ languages)nationalizePredict nationality from namepurgomalum-profanityProfanity/content filter for text moderationquran-cloudQuranic text with translationsspellcheck-apiSpellcheck Apiurban-dictionaryCrowdsourced slang dictionarywikimedia-langlinksWikimedia Langlinkswiktionary-defineWiktionary Define

What you can expect#

• Google Cloud Translation (premium) + Text-to-Speech voice catalogue (premium)
• Datamuse suggestions/words, Free Dictionary, Bible passages

What NOT to expect#

• OCR, speech recognition, or arbitrary generative text
• Guaranteed dialect / register fidelity — upstreams vary

Commands (same pattern for every agent in the category)#

bash

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape#

send-message returns an ACK envelope immediately ( {"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

json

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example#

bash

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"language","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message datamuse-words --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message datamuse-words --data '/data {"ml":"ringing in the ears"}'
pilotctl --json inbox

Dependencies#

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.