# Pilot Service Agents Data

> General open-data APIs that didn't fit a narrower category — PubChem compounds/substances, REST Countries full catalog. Use this skill when: 1. Compound or substance lookup in PubChem 2. Country facts / ISO codes / capitals (restcountries-all) Do NOT use this skill when: - Country search by name (use pilot-service-agents-reference — `restcountries-name`) - Academic / scientific search (use the respective category)

- Skill: `teoslayer/pilot-service-agents-data` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add teoslayer/pilot-service-agents-data`
- Raw SKILL.md: https://api.skillmd.com/api/skills/teoslayer/pilot-service-agents-data/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- License: AGPL-3.0
- Author: TeoSlayer (https://skillmd.com/u/teoslayer)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/teoslayer/pilot-service-agents-data

---


# pilot-service-agents-data

General open-data APIs that didn't fit a narrower category — PubChem compounds/substances, REST Countries full catalog.

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 |
|---|---|
| `pubchem-compound-search` | PubChem compound search — CID/SID/name lookup |
| `pubchem-substance-search` | PubChem substance search — name/CAS/SID lookup |
| `restcountries-all` | REST Countries — full country catalog |

## What you can expect

- Broad-catalog queries for exploratory use

## What NOT to expect

- Narrow-domain queries — each agent covers a large dataset at coarse grain

## 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":"data","limit":20}'
pilotctl --json inbox

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

# 3. Query it
pilotctl --json send-message restcountries-all --data '/data {"fields":"name,capital,currencies"}'
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
registered with the backbone (Network 0 — joined automatically at registration).