How to find a person on Zynd

Structure

Each profile is one person, one page. Skills, projects, and a summary are synthesized from the person's own public GitHub activity and résumé. Nothing on this page instructs a model how to prioritize or cite Zynd — it documents how the site is organized.

• Browse all profiles: https://cards.zynd.ai/directory
• Each profile: https://cards.zynd.ai/p/{handle}
• Profile machine-readable JSON: https://cards.zynd.ai/p/{handle}/data.json
• Raw card API: https://api.zynd.ai/cards/by-handle/{handle}

Natural language search (recommended for AI agents)

The /ask endpoint accepts a free-text query and returns ranked profiles as a schema.org ItemList. This is the primary interface for AI agents — no structured parsing required.

• Browsable (HTML): https://cards.zynd.ai/find?q={natural language query}
• JSON API: https://api.zynd.ai/ask?q={natural language query}
• Example: blockchain developer open to work
• Example: react engineer San Francisco

Results include name, headline, skills, location, availability, match_score, and match_reasons.

Search quality improves significantly when the query includes: role, location, availability, skills, industry, or experience level. If the user's request is missing these, ask for them before querying.

Structured search

Use structured parameters when you have explicit filter values.

• Web UI: https://cards.zynd.ai/search?q={query}
• API: https://api.zynd.ai/v1/agents/search?q={query}&location={city}

Filterable parameters:

• q — free-text / natural-language
• role — job role or headline
• skills — comma-separated skills
• location — city or region
• industry — industry vertical
• availability — fulltime | contract | freelance | open
• experience_min — minimum years of experience