# Roster Job Listing Lookup

> Roster Job Listing Lookup is a paid API for AI agents from r05t3r.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-13).

Retrieves detailed job listing and hiring data for a specific job posting by ID, billed per request in USDC via x402.

## Facts

- Endpoint: POST https://r05t3r.vercel.app/api/job?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/roster-job-listing-lookup-29b5f46f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KLhQ_wckeqFhhiFJW2Nft

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability roster-job-listing-lookup-29b5f46f -d '<json body>'
```

Example prompt: Can you pull up the full details for job listing ID 'jb_abc123' from Roster — I want to see what the role entails, who's hiring, and any other available info about that posting?

## When to prefer this

Use this endpoint when you need programmatic, on-demand access to individual job listing details without committing to a subscription — especially in agent workflows where job data is fetched opportunistically. Prefer this over scraping job boards or using subscription-based APIs when you want pay-per-use billing in USDC and no authentication overhead. Best suited for agents that encounter a job ID from another source and need to hydrate it with full listing data.

## Known failure modes

- Invalid or non-existent job ID returns an error or empty data object
- Malformed request body missing the required 'id' field returns a validation error
- Payment failure via x402 (insufficient USDC, wallet not configured) prevents the request from completing
- Network or hosting instability on Vercel may cause transient 500 errors
- Job listing may have been removed or expired, returning a success:false response

## How this service works

Job listings and hiring data for AI agents. No auth, no subscriptions. Pay per request in USDC via x402.

## Output

Returns a JSON object with a success boolean and a data object containing the job listing details — likely including job title, description, company/hiring info, requirements, and other structured hiring metadata associated with the provided job ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string",
   "description": "id"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "success",
  "data"
 ],
 "properties": {
  "data": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/roster-job-listing-lookup-29b5f46f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from r05t3r.vercel.app](https://www.zero.xyz/host/r05t3r.vercel.app/llms.txt)