Fix public-api skill: use clay-api-key header (not Bearer) and refresh stale search paths

[TenSpy-ai]

Summary

clay/skills/public-api/SKILL.md tells agents to send the API key "as a Bearer token against https://api.clay.com/public/v0". That returns 401 on every endpoint. The correct scheme, per Clay's own docs (https://developers.clay.com/public-api/authentication.md), is the clay-api-key: <key> header.

An agent following the skill as written burns its retries on 401s and concludes the key is bad.

Verified reproduction

Key minted with clay api-keys create (repo state: main as of 2026-07-10):

# As the skill instructs — fails:
curl -s -o /dev/null -w "%{http_code}" -H "Authorization: Bearer $KEY" \
  https://api.clay.com/public/v0/me       # -> 401

# Per developers.clay.com — works:
curl -s -o /dev/null -w "%{http_code}" -H "clay-api-key: $KEY" \
  https://api.clay.com/public/v0/me       # -> 200  {"user":...,"workspace":...}

Secondary fix: stale Search endpoint paths

The skill's "What it offers" section listed old routes. Verified against the live API:

Skill (old)	Result	Current	Result
GET /searches/fields?source_type=companies	404	GET /search/filters-mode/fields?source_type=companies	200 (30 fields)
POST /searches	404	POST /search/filters-mode	400 (path exists, wants a body)

Pagination route left to the API reference rather than asserting an unverified path.

Changes (one file)

• Auth: replace the Bearer sentence with the clay-api-key header + a /v0/me smoke-test.
• Search paths: update the fields and start-search routes to the verified /search/filters-mode/... paths.

🤖 Generated with Claude Code