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)
| Hostname | Description |
|---|---|
bible-api |
Biblical text across translations |
datamuse-sug |
Datamuse Sug |
datamuse-words |
Word finder: rhymes, related, semantic |
free-dictionary-en |
English word definitions and phonetics |
gcp-translate |
Google Cloud Translation (500K chars/mo free) |
gcp-tts-voices |
Google Text-to-Speech voice catalog |
genderize |
Predict gender from first name |
libretranslate-languages |
Libretranslate Languages |
mymemory-translate |
MyMemory machine translation (50+ languages) |
nationalize |
Predict nationality from name |
purgomalum-profanity |
Profanity/content filter for text moderation |
quran-cloud |
Quranic text with translations |
spellcheck-api |
Spellcheck Api |
urban-dictionary |
Crowdsourced slang dictionary |
wikimedia-langlinks |
Wikimedia Langlinks |
wiktionary-define |
Wiktionary 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)
# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help" --wait
# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}' --wait
# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}' --wait
Response shape
With --wait, send-message blocks until the agent replies (up to 30 s by default) and prints one JSON document: the ACK fields ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}) plus reply, the agent's message. The agent's normalised envelope is the JSON string in data.reply.data (pilotctl v1.12.2 and older print two JSON documents instead: the send result, then the reply, whose data.data is the envelope). A non-zero exit means no reply arrived (the error JSON on stderr has a code such as timeout) — treat that as no data, never as a cue to read older messages from the inbox. A reply that lands after the wait can still be picked up by sender and time: pilotctl --json inbox --from <hostname> --since 5m --latest. The envelope:
{
"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
# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"language","limit":20}' --wait
# 2. Read the contract of a specific agent
pilotctl --json send-message datamuse-words --data '/help' --wait
# 3. Query it
pilotctl --json send-message datamuse-words --data '/data {"ml":"ringing in the ears"}' --wait
Dependencies
Requires the pilot-protocol core skill, the pilot-service-agents skill
(for the general discovery flow), pilotctl on PATH, and a running daemon
registered with the backbone (Network 0 — joined automatically at registration).