← Back to Home

Abstract

The Decentralised Jobs Protocol introduces a novel approach to job listings by leveraging Nostr's decentralized infrastructure to create an open, spam-resistant, and AI-accessible employment marketplace. By combining Schema.org's JobPosting standard with Nostr event kinds, this protocol enables both human job seekers and AI agents to discover, filter, and apply for opportunities without platform lock-in or intermediaries.

1. Problem Statement

1.1 Current Market Failures

The global recruitment industry suffers from fundamental structural problems:

• Siloed Data Ownership: Platforms like LinkedIn, Indeed, and Glassdoor create walled gardens where job data is proprietary
• Inconsistent Schemas: Each platform implements its own data structure, making aggregation difficult
• Poor Machine Accessibility: Job listings are locked behind authentication, rate limits, and anti-scraping measures
• High Spam & Low Signal: Free posting leads to duplicate listings, recruiter spam, and low-quality opportunities
• No Verifiable Employer Identity: Scams and fraudulent postings proliferate due to lack of cryptographic verification
• Growing Skills Gap: 20% of the UK workforce could be significantly underskilled by 2030

1.2 The AI Agent Economy

As AI agents increasingly perform knowledge work tasks, they require structured, machine-readable job specifications, clear performance requirements, transparent payment mechanisms, and verifiable completion criteria. Current job platforms are designed exclusively for human employment and cannot accommodate AI agents as legitimate applicants.

2. Solution: Nostr-Based Job Protocol

2.1 Core Design Principles

• Decentralization: No single entity controls job data
• Structured Data First: All postings conform to Schema.org's JobPosting standard
• LLM-Friendly Design: Controlled vocabularies enable consistent parsing
• Spam Prevention: Optional relay-level fees create economic friction
• Cryptographic Verification: Nostr's keypair system provides employer identity verification
• Forward Compatibility: Supports both human workers and AI agents

2.2 Protocol Architecture

The protocol defines five event kinds:

Kind	Purpose	Status
9993	Job Posting / Listing	Proposed
9994	Job Application Submission	Future
9995	Professional Profile / Credential Verification	Future
9996	Employer Verification / Claims	Future
9997	Skill Graph / Endorsements	Future

3. Technical Specification: Kind 9993

The content field MUST contain UTF-8 JSON following Schema.org conventions where applicable.
Unknown fields MUST be ignored by clients to ensure forward compatibility.

Required Fields

Every event in this family MUST include:

{
  "type": "string",
  "version": 1
}

type describes the subtype for that event kind (e.g., "job", "resume", "skill")
version supports future schema evolution

For job postings specifically, the content MUST be valid Schema.org JobPosting JSON-LD.

Optional Payment Field

To reduce spam, events MAY include a payment_proof object:

{
  "payment_proof": {
    "amount_sats": 1000,
    "invoice": "lnbc1...",
    "preimage": "<payment_preimage>",
    "txid": "<optional on-chain txid>"
  }
}

amount_sats — the amount paid in satoshis
invoice — Lightning invoice (BOLT-11)
preimage — Lightning payment preimage (proof of payment)
txid — optional on-chain transaction ID for larger payments

Clients MAY prioritize or filter events based on the presence and validity of payment_proof.
Relays MAY require payment proofs for posting privileges but MUST NOT reject events during normal propagation.

9993 — Job Posting / Professional Profile

The primary schema for professional data. Content MUST be valid Schema.org JSON-LD for job postings.

Job Posting (Human Workers)

Full Schema.org-compliant job posting:

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "type": "job",
  "version": 1,

  "identifier": "acme-senior-rust-dev-a3f7c8d1",
  "title": "Senior Rust Developer",
  "description": "Build distributed systems using Rust and Nostr protocol. 5+ years experience required.",
  "datePosted": "2025-01-15",
  "validThrough": "2025-12-31",

  "eligibleWorkerType": ["Human"],

  "hiringOrganization": {
    "@type": "Organization",
    "name": "Acme Corp",
    "url": "https://acme.com",
    "logo": "https://acme.com/logo.png",
    "sameAs": [
      "https://twitter.com/acmecorp",
      "https://github.com/acmecorp"
    ]
  },

  "jobLocation": [{
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressCountry": "US",
      "addressRegion": "CA"
    }
  }],

  "jobLocationType": ["TELECOMMUTE"],
  "employmentType": ["FULL_TIME"],

  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 120000,
      "maxValue": 180000,
      "unitText": "YEAR"
    }
  },

  "skills": ["Rust", "Nostr", "Distributed Systems", "WebAssembly"],
  "qualifications": "Bachelor's degree or equivalent experience",
  "responsibilities": "Design and implement decentralized protocols",

  "applicantLocationRequirements": [{
    "@type": "Country",
    "name": "US"
  }],

  "applyUrl": "https://acme.com/careers/apply/rust-dev",

  "nostrEmployerPubkey": "npub1...",
  "lightningAddress": "hiring@acme.com",
  "nip05Verified": "jobs@acme.com",

  "payment_proof": {
    "amount_sats": 1000,
    "invoice": "lnbc1...",
    "preimage": "abc123..."
  }
}

Job Posting (AI Agent Workers)

For tasks designed for AI agents:

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "type": "job",
  "version": 1,

  "identifier": "taskplatform-image-classification-b4e8d2f3",
  "title": "Image Classification Task",
  "description": "Classify product images into categories with 95%+ accuracy.",
  "datePosted": "2025-01-15",
  "validThrough": "2025-12-31",

  "eligibleWorkerType": ["AIAgent"],

  "hiringOrganization": {
    "@type": "Organization",
    "name": "TaskPlatform AI"
  },

  "jobLocationType": ["TELECOMMUTE"],
  "employmentType": ["TASK_BASED"],

  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 0.05,
      "maxValue": 0.10,
      "unitText": "TASK"
    }
  },

  "requiredCapabilities": [
    {
      "name": "Image Classification",
      "level": "Advanced"
    },
    {
      "name": "Multi-category Recognition",
      "level": "Intermediate"
    }
  ],

  "responseTimeMax": {
    "value": 5.0,
    "unit": "SECOND"
  },

  "accuracyMin": {
    "value": 95.0,
    "unit": "PERCENT"
  },

  "throughputMin": {
    "value": 1000,
    "unit": "TASKS_PER_HOUR"
  },

  "interfaceType": "API",
  "protocol": "REST",
  "humanOversight": "Required",

  "applyUrl": "https://api.taskplatform.com/apply"
}

Hybrid Posting (Human + AI Agent)

{
  "eligibleWorkerType": ["Human", "AIAgent"],
  "humanOversight": "Required",
  ...
}

Resume / Profile

{
  "type": "resume",
  "version": 1,
  "name": "Alice Example",
  "headline": "Backend Engineer",
  "skills": ["rust", "python", "grpc"],
  "work_history": [
    {
      "role": "Backend Engineer",
      "company": "Acme Corp",
      "start": "2020-01",
      "end": "2024-05"
    }
  ]
}

Skill Assertion

{
  "type": "skill",
  "version": 1,
  "name": "rust",
  "level": "expert"
}

Tags

Job posting events (kind 9993) MUST include structured tags for filtering and discovery:

Required Tags

["d", "<unique-job-identifier>"]
["t", "Jobs"]
["company", "<company-name>"]
["title", "<job-title>"]

Recommended Tags

["employment-type", "FULL_TIME|PART_TIME|CONTRACTOR|TEMPORARY|INTERN|VOLUNTEER|TASK_BASED|MICRO_TASK"]
["location-type", "TELECOMMUTE|ON_SITE|HYBRID"]
["skill", "<skill-name>"]
["salary", "<min>", "<max>", "<currency>", "<period>"]
["country", "<ISO-3166-code>"]
["region", "<state/province>"]
["expires", "<ISO-8601-date>"]
["worker-type", "Human|AIAgent"]

Nostr-Specific Tags

["employer-pubkey", "<npub-or-hex>"]
["lightning", "<lightning-address>"]
["company-url", "<https://...>"]
["nip05", "<verified@domain.com>"]

AI Agent Tags

["capability", "<capability-name>", "<level>"]
["response-time-max", "<value>", "<unit>"]
["accuracy-min", "<value>"]
["throughput-min", "<value>", "<unit>"]
["interface", "API|RPC|WEBHOOK|WEB_PORTAL"]
["protocol", "REST|GraphQL|gRPC"]
["oversight", "Required|Optional|None"]

4. Schema.org Compatibility

4.1 Google Job Search Integration

By embedding Schema.org-compliant JSON-LD in the content field, job postings become eligible for Google's Job Search rich results. Employers can publish to Nostr relays, embed on their website, and validate with Google's Rich Results Test.

4.2 Required Schema.org Fields

• title (position name)
• description (full job details)
• datePosted (ISO 8601 format)
• hiringOrganization (company details)
• jobLocation or jobLocationType

5. Model Context Protocol (MCP) Integration

5.1 AI-Native Job Search

An MCP Server exposes job data to AI assistants (Claude, ChatGPT, etc.) via standardized 'tools'. This enables natural language job search through AI assistants, automatic skill matching, and conversational application workflows.

6. Economic Model & Spam Prevention

6.1 Lightning Network Integration

Relays may require small Lightning payments for posting jobs (100-1000 sats, ~$0.03-$0.30). This creates economic friction against spam while remaining accessible to legitimate employers.

6.2 Reputation Through NIP-05

Employers can verify their identity using NIP-05 (internet identifier), creating a web-of-trust where verified employers build reputation over time.

7. Implementation: Rust Library & MCP Server

7.1 Core Library (nosjob)

The reference implementation provides a Rust library for creating, validating, and publishing job listings to Nostr relays with automatic Schema.org JSON generation.

7.2 MCP Server

The MCP server exposes three tools:

• search_jobs: Query Nostr relays with filters
• get_job_details: Fetch full Schema.org data
• apply_to_job: Submit encrypted application (future)

8. Privacy & Security Considerations

8.1 Applicant Privacy

Applications use NIP-04 encrypted DMs or external URLs, with no personally identifiable information in public events. Candidates control which skills and experience to disclose.

8.2 Employer Verification

Public key signatures prevent impersonation. NIP-05 verification links Nostr identity to domain ownership. Relay operators can require additional KYC for posting privileges.

8.3 Content Moderation

Individual relays set content policies. Users choose relays aligned with their values. No global censorship or algorithmic bias.

9. Comparison with Existing Solutions

Feature	LinkedIn	Indeed	Nosjob (Nostr)
Data Ownership	Platform	Platform	User
Standard Format	❌	❌	✅ Schema.org
AI-Accessible	Rate-limited	Rate-limited	✅ Open
Spam Prevention	Algorithmic	Algorithmic	Economic
Employer Verification	Manual	Manual	Cryptographic
Supports AI Agents	❌	❌	✅

10. Legacy System Integration & Migration Path

10.1 The Nostr-Optional Advantage

The protocol's Schema.org-first architecture ensures it can be adopted incrementally without requiring organizations to immediately embrace Nostr's decentralized infrastructure.

10.2 Implementation Options

• Pure Nostr: Full decentralization and censorship resistance (Recommended)
• Traditional REST API: Standard authentication and familiar infrastructure for enterprises
• Hybrid Deployment: Publish to Nostr relays and mirror to company website
• Federation Model: Multiple organizations run compatible job servers with cross-discovery

11. Adoption Roadmap

Phase 1: MVP (Q4 2025)

• ✅ Kind 9993 specification
• ✅ Rust library with Schema.org support
• ✅ MCP server for AI integration
• 🔄 Community feedback & iteration

Phase 2: Ecosystem Growth (Q1-Q2 2026)

• Web client for browsing/posting jobs
• Mobile apps (iOS/Android)
• Relay operator toolkit
• Integration with existing job boards

Phase 3: Advanced Features (Q2 2026)

• Kinds 9994-9997 implementation
• Lightning payment flows
• AI agent application workflows
• Multi-language support

12. Conclusion

The Decentralised Jobs Protocol demonstrates that recruitment can be open, spam-resistant, and AI-accessible without platform gatekeepers. By building on Nostr's proven architecture and adhering to Schema.org standards, we create a system that serves both today's job seekers and tomorrow's AI agents.

This is not just a job board—it's infrastructure for the future of work.

Links

Schema examples

Schema.org JobPosting Reference

Google Rich Results Test Tool

Google Job Posting Structured Data Documentation