A job market built to be searched by people and agents.

The launch API is read-only and does not require an API key. Search with GET /api/v1/search, retrieve one public item with GET /api/v1/listings/{id}, or inspect disciplines through GET /api/v1/categories.

Example: /api/v1/search?kind=role&country=US&discipline=AI%20%26%20Data&workplace=remote&limit=25

• q searches title, organization, discipline, and public description.
• kind accepts role or talent.
• country accepts US or CA. Every public record includes workCountry and a neutral eligibility object.
• discipline, location, and workplace narrow discovery.
• limit accepts 1–100; cursor continues a result set.
• Employer roles and talent signals rank separately inside each discipline and country. categoryRank is the true rank for that side, discipline, and country.
• Results order by disclosed paid rank, then oldest first for equal amounts.

Only listings that are both published and public can appear. The API never returns account email, owner ID, resume bytes or metadata, private contact details, storage keys, matched-only posts, invite-only posts, drafts, or moderation records.

A scheduling URL appears only when its owner explicitly selects public booking visibility. Calendly and Google Calendar credentials are never stored by this link-based integration.

Market-access declarations, network-country signals, review reasons, and moderation records are private and never returned by the public recruiting API.

• Respect listing status, visibility, candidate consent, and platform rate limits.
• Do not infer or enrich protected characteristics.
• Apply the current-work-authorization and no-sponsorship rule equally. Do not use nationality, birthplace, race, ethnicity, accent, religion, or a proxy for any protected characteristic.
• Do not scrape private surfaces, bypass authentication, spam candidates, or blind-submit profiles.
• Money changes labeled category visibility only; it does not change qualifications, consent, or private-data access.
• OutbidJobs provides the posting board and API, not recruiting representation or hiring decisions.

The OpenAPI 3.1 document is available at /api/v1/openapi. Agent discovery guidance is available at /llms.txt. The beta schema may gain fields, but private fields will not be added to public responses without an explicit visibility control.