OJCP
OJCP is an open standard protocol that defines how AI agents discover, evaluate, and apply for job opportunities across multiple job boards and ATS platforms. Providers expose their capabilities via a manifest at /.well-known/ojcp.json, allowing agents to auto-discover search, detail, and application endpoints without hardcoding vendor-specific URLs. The protocol standardizes job application flows into a normalized taxonomy, supports consent-first privacy via resume embeddings, and includes identity verification with JWS proofs. Agents can rank job results using CandidateContext parameters and track application status through the hiring pipeline. OJCP is governed by an independent steering committee and is designed to compose with MCP and schema.org.
OJCP is an open standard protocol, integrating with MCP, schema.org, Workday, and Greenhouse. InnovaAI scores it 3.8/10 for agency adoption, best for Founder, Engineering Lead, and Operations Manager roles handling 5+ client meetings per week.
Agency Audit
OJCP is an open standard protocol that lets AI agents discover, evaluate, and apply for job opportunities across multiple job boards and ATS platforms without manual intervention. For digital agencies, this is relevant only if your team operates an AI agent platform, staffing service, or job-board integration as an internal tool. Most traditional creative and strategy agencies will not adopt OJCP directly; it's designed for vendors and platforms, not end-user teams. If your agency builds or maintains agent-based recruitment workflows, OJCP standardizes the discovery and application pipeline, reducing custom integration work.
2recommended
24/mo
No paid plan published
High
Illustrative scenario. Not a guarantee. Net capacity needs a verified paid base plan, and none is published for this service, so it is not modeled. Hours saved come from the service estimate; implementation, taxes, and unprovided usage charges are excluded.
- Founder handling AI agent platform integration and maintenance
- Engineering Lead handling multi-vendor job board and ATS mapping
- Operations Manager handling agent-driven job application pipeline management
- Your agency is a traditional creative, design, or strategy shop with no internal AI agent platform or recruitment automation; OJCP has no value in that context.
- You do not currently integrate with multiple job boards or ATS platforms; OJCP's benefit is standardization across vendors, not single-vendor adoption.
- Your team lacks in-house engineering capacity to implement MCP tooling or integrate a protocol standard into your existing stack; OJCP requires technical implementation, not configuration.
Internal Adoption Path
No paid plan published
24 hr/mo
2 seats × 12 hr each
$1,800/mo
modeled at $75/hr labor rate
No paid plan published
Illustrative scenario. Not a guarantee. No verified paid base plan is published for this service, so subscription cost and net capacity are not modeled. Implementation, taxes, and unprovided usage charges are excluded.
Platform Features
Core capabilities of OJCP
Manifest-based capability discovery
Job boards and ATS platforms expose a /.well-known/ojcp.json manifest that allows your AI agents to automatically detect available search, detail, and application endpoints without hardcoding vendor-specific URLs. Reduces integration maintenance overhead for engineering teams managing multi-vendor job pipelines.
Normalized job application paths
OJCP standardizes the apply mechanism across different ATS vendors (Workday, Greenhouse, Lever, Indeed) into a single taxonomy, so your agent platform does not need custom logic for each vendor's form structure or submission flow. Cuts custom apply-path code by consolidating vendor differences into a single interface.
Fit scoring with consent-first privacy
Agents can evaluate job fit using resume embeddings and CandidateContext without transmitting personally identifiable information to job boards. Operations and compliance teams benefit from privacy-by-design; no need to audit custom data-handling logic for each integration.
Agent-aware ranking and search
The search_jobs tool accepts CandidateContext parameters so agents can rank results by fit before presenting them to users. Improves relevance in agent-driven job discovery workflows without requiring post-fetch filtering logic in your platform code.
Application status tracking
OJCP includes a mechanism to track application status through the hiring pipeline, allowing your agent platform to provide real-time feedback on submitted applications. Reduces manual status-check workflows for operations teams managing high-volume agent-driven submissions.
Identity verification with JWS proofs
Agents can verify their identity to job boards using JWS proofs and verifier manifests, enabling secure agent-to-board communication without exposing credentials in plaintext. Simplifies credential management for engineering teams running multiple agent instances across different job sources.
What Makes OJCP Different
Unique advantages vs similar tools in this niche
Open standard protocol for agent-job interactions
vs Proprietary job APIs and fragmented application mechanismsOJCP defines a shared protocol so AI agents and job providers speak the same language, with structured discovery and normalized apply paths.
MCP-native tools
vs Custom APIs requiring bespoke integrationsOJCP tools are valid MCP tools, callable by any MCP client out of the box, reducing integration effort.
Consent-first privacy with PII-free fit scoring
vs Traditional resume transmission with PII exposureResume embeddings enable fit-scoring without transmitting PII, and candidate data is opt-in and scoped.
Value Equation
Outcome-likelihood-time-effort assessment for OJCP
Value math requires real pricing
The Value Equation (dream outcome × likelihood ÷ time × effort) feeds directly into ROI math. OJCP has no published pricing, so we hold this section until real numbers are available.
Contact OJCPPricing
Pricing data not yet available for OJCP.
Reality Check
OJCP is a protocol standard, not a consumer product. Adoption requires your team to either build MCP-native tooling around it or integrate it into an existing agent platform. There is no off-the-shelf dashboard or UI; implementation complexity depends entirely on your current tech stack and whether you're already running AI agents.
High effort: requires technical configuration and team training
How This Accelerates White-Label Services
Who It's For
- ✓ai-agent-platforms
- ✓job-boards
- ✓ats-vendors
- ✓staffing-agencies
Acceleration Steps
- 1Schedule onboarding with the vendor
- 2Configure discover job opportunities via /.well-known/ojcp.json manifests
- 3Connect MCP
- 4Launch your first client project
Academy for OJCP
Work through it in order: the course for this service first, then the modules behind it.
No Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Wiring Over WidgetsConcept
The AI agent itself is a commodity, but the value for agencies lies in the integration layer: connecting a pre-built agent to a client's CRM, calendar, and review cycle. This framework shifts focus from selecting the 'best' agent to mastering the wiring process. For example, an agency using Vendasta's white-label AI receptionist for a local business must configure it to match the client's booking rules and follow-up cadence, turning a generic tool into a tailored service. As agentic AI adoption grows (77% of decision-makers now run agents in production), clients expect this customization. Agencies that treat agents as components and invest in repeatable wiring processes can charge retainers for ongoing optimization, rather than one-off setup fees.
- Wiring Over WidgetsConcept
The AI agent market sells finished workers, but the strategic value for agencies lies not in the agent itself, which is increasingly a commodity, but in the wiring that connects it to a specific client's CRM, calendar, and review cycle. This framework, 'Wiring Over Widgets,' argues that agencies that treat agents as components rather than products win. The agent is the widget; the wiring is the integration, customization, and ongoing optimization that turns a generic tool into a tailored solution. For example, a white-label platform like Vendasta provides AI employees, but the agency's role is to configure them for each local business's unique lead flow and follow-up process. This wiring is where retainer pricing originates, as it requires ongoing maintenance and adjustment. Recent research shows that 88% of B2B marketers face foundational gaps, meaning clients need help not just deploying agents, but ensuring their operations can support them. Agencies that master the wiring can charge a premium for the irreducible value they add.
- Integration MoatConcept
The Integration Moat framework holds that the durability of an AI agent engagement is determined by how deeply the agent is wired into a client's existing systems, not by the agent's underlying capability. Since the agent itself is increasingly a commodity, the switching cost for the client lives in the integrations: the CRM fields mapped, the calendar sync, the review-cycle triggers, and the exception-handling rules. Agencies that invest in this wiring create a moat that competitors offering generic agents cannot cross. For example, a white-label platform like Vendasta lets an agency deploy an AI receptionist for a local business, but the real value is in configuring it to the client's booking flow and follow-up cadence. With 77% of AI decision-makers now running agentic AI in production, clients expect this depth, and agencies that deliver it convert one-off projects into retainers.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- AI Agents Rule: Wire the Agent, Not the ProductEvaluation Rule
Treat the AI agent as a commodity component and focus your value on the integration into the client's specific workflows, systems, and review processes.
- AI Agents Rule: Wire the Agent, Not the ProductEvaluation Rule
Treat the AI agent as a commodity component and charge for the integration into the client's specific systems and workflows.
- The Productized Agent Trap: Why AI Agent Services Stall Without Client-Specific WiringFailure Pattern
- The Agent-as-Product Trap: Why AI Agent Services Stall Without Client-Specific WiringFailure Pattern
8 modules selected for OJCP
Frequently Asked Questions
Answers about pricing, setup
OJCP is an open standard protocol that defines how AI agents interact with job boards and ATS platforms. It provides MCP-native tools (search_jobs, get_job_detail, begin_application) that agents can call, standardizes job application flows across vendors, and includes consent-first privacy mechanisms so agents can evaluate fit without transmitting PII. Providers expose their capabilities via a manifest at /.well-known/ojcp.json, allowing agents to auto-discover endpoints.
OJCP is an open standard protocol governed by an independent steering committee. There is no per-seat licensing fee; adoption is free. Costs arise only if you hire engineering resources to implement MCP tooling or integrate OJCP into your agent platform.
Engineering and operations teams benefit most. Engineers reduce integration maintenance by adopting a standardized protocol instead of maintaining custom vendor-specific code. Operations teams managing high-volume agent-driven job applications gain real-time status tracking and privacy-by-design compliance. Founders evaluating agent platform architecture benefit from avoiding proprietary lock-in by composing with an open standard.
Hours saved depend on your current integration footprint. If your engineering team maintains custom apply-path logic for 3+ ATS vendors, OJCP can reduce that maintenance burden by 4-6 hours per month per vendor by consolidating vendor-specific code into a single normalized interface. If you operate a single job board, OJCP provides minimal time savings.
Rollout complexity is high for most agencies because OJCP is a protocol standard, not a product. Implementation requires engineering effort to build or integrate MCP tooling, map your existing job-discovery or application workflows to OJCP endpoints, and test across multiple job boards. Expect 2-4 weeks of engineering time for a basic integration.
OJCP is designed to work with any job board or ATS that publishes an OJCP manifest. Known supported platforms include Workday, Greenhouse, Lever, and Indeed. If your agency uses a niche or proprietary ATS, check whether the vendor has published an OJCP manifest at their /.well-known/ojcp.json endpoint.