The App Store, for agents

1. Today

What an agent can do

There is no agent credential yet: no API token, API key or service account. Store data needs a member’s Zerg SSO session in their own browser, so an agent works with that person.

• Read the public documents

  The instructions, the API reference, the skill, the public app showcase and service health need no sign-in.

• Guide a signed-in person

  Point them to Discover, search, an app, Create or My apps in their store at /o/{org}.

• Read data they share

  They open a store JSON address in their own browser and share it; the API reference explains every field.

• Draft listings and bounties

  Prepare the brief, name, tagline, description, categories and tags; they enter and save it.

Not available today

• Call store routes without the person: a read answers 401 authentication_required, and a write is refused first with 403 cross_origin_mutation.
• Build, submit or publish an app. Agent builds are coming soon; a saved listing is a private draft with no code.
• Use the store’s built-in assistant from outside. It runs for signed-in members inside the store.

2. Access

Access and secrets

Zerg SSO browser session

Held by a member who signed in. It stays in their browser and lasts at most 12 hours. Agents never use it.

Agent token or API key

Does not exist yet, so a person cannot issue one and there is nothing to keep in a secret manager.

Internal tool credential

Minted by the store for its own read-only assistant. It is never issued to people or agents.

Store membership follows the organization’s Zerg directory. An organization admin adds people and changes their roles.

3. Work

Work with a signed-in person

1. Check the service: curl -fsS https://apps.zergai.com/api/health.
2. Have the person sign in at https://apps.zergai.com/login and open their store at /o/{org}.
3. Ask them to share what you need, for example the JSON at /api/v1/appstore/orgs/{org}/apps?q=expenses opened in their browser.
4. Prepare listings, bounties, reviews or feedback for them to enter. They save; nothing is published from a draft.

# Without the person's session, a store read answers 401
curl -sS https://apps.zergai.com/api/v1/session

The API reference lists every route, what it needs, its request and response shapes, and the errors a person or an agent can meet.

4. Skill

Install the skill

The zerg-appstore skill uses these public URLs only. Install it where your agent loads skills: Codex reads ~/.codex/skills, Claude Code reads ~/.claude/skills.

mkdir -p "$HOME/.codex/skills/zerg-appstore"
curl --fail --show-error --location https://apps.zergai.com/skills/zerg-appstore/SKILL.md \
  --output "$HOME/.codex/skills/zerg-appstore/SKILL.md"

5. Rules

What an agent must not do

• Never take, copy or replay a browser cookie or browser storage, or drive the person’s signed-in browser.
• Never accept a password, SSO code or session from anyone. Credentials never go in chat, URLs or command arguments.
• Never use operator tools, scripts, database access or an administrator session to get around a refusal.
• Never put code, patches, files or uploads into a brief, listing, review, bounty or feedback. People describe; agents build.
• Never probe store slugs: an unknown store, a store you do not belong to and a malformed slug all answer the same 404.
• Never read a null number as zero. The store shows “not measured yet” rather than estimate.