Y Combinator Startup Job Openings: Software Engineering Roles

omnial/startup-job-listings-ycombinator

Returns up to 30 job openings in the software engineering category at Y Combinator-backed startups. Each has its ID, title, employment type, location, a finer role category (such as full stack or machine learning), the salary range when listed, the hiring company's name, short name, YC batch and one-line description, and a link to the opening, plus the count returned. The role input accepts only the software engineering category, the one value tested.

activeper callv1

Price

Up to $0.0137 per call; you pay what the call used

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

Y Combinator

Data from Y Combinator.

Use it

Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

For developers: the calls your assistant makes

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/startup-job-listings-ycombinator" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/startup-job-listings-ycombinator" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/startup-job-listings-ycombinator", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/startup-job-listings-ycombinator", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0137

Updated: Nov 1, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "role"
  ],
  "properties": {
    "role": {
      "enum": [
        "software-engineer"
      ],
      "type": "string",
      "description": "The role category; only \"software-engineer\", the one value tested."
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "properties": {
        "jobs": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "id": {
                "type": "number",
                "description": "The opening's ID."
              },
              "type": {
                "type": "string",
                "description": "The employment type, such as full-time."
              },
              "title": {
                "type": "string",
                "description": "The job title."
              },
              "salary": {
                "type": [
                  "string",
                  "null"
                ],
                "description": "The salary range as text, or null when not listed."
              },
              "job_url": {
                "type": [
                  "string",
                  "null"
                ],
                "description": "A link to the opening."
              },
              "location": {
                "type": "string",
                "description": "Where the job is based: cities and remote regions, separated by slashes."
              },
              "company_name": {
                "type": "string",
                "description": "The hiring company's name."
              },
              "company_slug": {
                "type": "string",
                "description": "The hiring company's short name, in lower case."
              },
              "company_batch": {
                "type": "string",
                "description": "The company's YC batch: a season letter and a two-digit year."
              },
              "role_category": {
                "type": "string",
                "description": "A finer role category, such as full stack, backend or machine learning."
              },
              "company_description": {
                "type": "string",
                "description": "The company's one-line description."
              }
            }
          },
          "description": "One entry per opening."
        },
        "count": {
          "type": "number",
          "description": "The number of openings returned."
        }
      }
    },
    "status": {
      "type": "string",
      "description": "success when the lookup returned data."
    }
  },
  "description": "Openings in the software engineering category at YC-backed startups."
}