Use Autojob with an AI assistant

Connect an AI assistant to search jobs, upload your resume, submit applications, and track results in your Autojob account.

Connect from your conversation

Ask your assistant to connect to Autojob. It opens a sign-in window. Continue with Google or email, connect your account, and return to your conversation. Your assistant can then find matches and manage applications.

For assistants that can make web requests, Autojob provides a connection link. You do not need to enter a server URL, copy a token, or configure a callback.

Connection instructions for assistants

Start with POST https://autojob.org/oauth/device/start, sending JSON {"client_name":"Your assistant name","resource":"https://autojob.org/api/v1"}. Keep the returned device_code private. Show the user verification_uri_complete as a “Connect Autojob” link, or open it in a sign-in window. Display the user_code next to the link so the user can match the connection.

Poll the returned token_endpoint at the returned interval using form fields grant_type=urn:ietf:params:oauth:grant-type:device_code, device_code, client_id, and resource. On authorization_pending, wait. On slow_down, increase the interval by five seconds. Stop on access_denied or expired_token. Once connected, use the access token for the documented API. Never ask the user to paste tokens into the conversation.

For MCP clients, use https://autojob.org/mcp. Public tool discovery advertises OAuth, and protected tool calls return a native sign-in challenge. Clients handle the connection window. The standard PKCE flow remains available.

What your assistant can do

Search jobs, read job details, upload a PDF or DOCX resume, update your profile and preferences, find matches, submit applications using your credits, start or stop Auto Mode, and read application results and employer messages. Billing tools create links for you to complete checkout or manage your plan.

Connected agents

Loading connections…

API documentation

The OpenAPI specification describes every endpoint under /api/v1/. The agent directory links to product information and current pricing.

Account connection

Discover OAuth at /.well-known/oauth-authorization-server. Register a public client at /oauth/register with a client name and exact redirect URIs. Use the authorization-code flow with S256 PKCE and the autojob scope. Set the resource to https://autojob.org/mcp for MCP or https://autojob.org/api/v1 for REST, including when exchanging or refreshing tokens. Access tokens last one hour; refresh tokens last up to 30 days and rotate on use. Disconnecting an agent immediately invalidates its tokens.

Uploads and applications

POST a filename and standard base64 content to /api/v1/resumes (maximum 15 MB decoded). Poll the returned status URL until ready; this adopts the parsed resume into your account. Errors or expiration require a new upload. In MCP, use upload_resume and get_resume_status.

POST up to 50 job IDs to /api/v1/applications with an Idempotency-Key header of 8–128 letters, numbers, dots, underscores, colons, or hyphens. Keep the key and body unchanged when retrying. MCP takes the same key as idempotency_key. Reusing a key with a different batch returns a conflict. Application IDs let you track each result. Queued and waiting_credit are pending states; only submitted means confirmed submission.

Results and limits

Use returned pagination cursors. Agent actions allow 120 requests per minute per account. Errors use HTTP status codes and a detail message; MCP returns a status, data, and an error flag. REST attachment downloads return binary data. MCP returns base64 for attachments up to 5 MB. No message-sending tool is provided.