Cursor
Grok Bot
Grok
MuseTitle77/100
Search
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Search the YC network. Set `entity` to choose what to search. `post` and `posts` are aliases for `forum`. The first search response includes available_filters and filter_value_examples (common values for each filter used, not the values in the results); use these to refine subsequent searches. When the user asks to export, download, or receive Algolia-backed search results as a CSV, call this search tool with attach_csv: true and csv_filename. Do not use csv.create for search result exports. - employers: Find existing employers, including non-YC companies, and their canonical Employer IDs. query accepts a company name, alias, website/domain, or LinkedIn company URL. poc accepts a contact's name, email, or LinkedIn profile URL. It searches visible Bookface profiles and contacts in your current company's CRM. Email searches match existing CRM contacts by their full email address; use query to search a company domain. When query and poc are both supplied, both must match. Results preserve ambiguity: inspect name, website, LinkedIn URL, and matched_by before selecting an employer_id. These IDs are Employer IDs, not Bookface company IDs or Sales CRM customer-row IDs. has_more also signals a capped candidate search; narrow query or poc when it is true. Search does not create employers or research unknown companies on the web. Tips: Use query for a company and poc for a person. Both together narrow the results. Employer IDs are distinct from Bookface company IDs; inspect identity fields before selecting a match. - companies: Search for YC companies by name, description, or keywords. Results include each company's primary YC partner in the partners field. Available filters and the most common values: batch: "Unspecified", "W22", "S21", "W21", "W23"; status: "Not YC", "Active", "Inactive", "Acquired", "Public"; regions: "Unspecified", "America / Canada", "United States of America", "Remote", "Partly Remote"; industry: "Unspecified", "B2B", "Consumer", "Healthcare", "Fintech"; isHiring: "false", "true"; nonprofit: "false", "true"; team_size: "2", "3", "0", "4", "5"; subindustry: "Unspecified", "B2B", "B2B -> Engineering, Product and Design", "B2B -> Infrastructure", "B2B -> Productivity"; batch_groups: "Unspecified", "W22", "S21", "W21", "W23"; latest_round_raised: "Series A", "Seed", "Series B", "Series C", "Series D+". Available extra_fields: active_positions.avatar_thumb, active_positions.bio, active_positions.first_name, active_positions.last_name, active_positions.model_id, active_positions.model_type, active_positions.position_end, active_positions.position_start, active_positions.search_path, active_positions.title, active_positions.user_id, batch_display_name, batch_groups, current_location, current_region, former_names, iid, inactive_positions.avatar_thumb, inactive_positions.bio, inactive_positions.first_name, inactive_positions.last_name, inactive_positions.model_id, inactive_positions.model_type, inactive_positions.position_end, inactive_positions.position_start, inactive_positions.search_path, inactive_positions.title, inactive_positions.user_id, indexed_at, industries, industry, isHiring, latest_round_raised, legal_entity_names, legal_name, long_description, nonprofit, objectID, participated_batch, participated_batch_groups, regions, small_logo_thumb_url, sub_batch_group, sub_participated_batch_group, subindustry, team_size, top_company, visibility, website. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Always include long_description in extra_fields to judge relevance. IMPORTANT: batch filter values use short names like "W25", "P26", "F25" — NOT the long format "w2025", "p2026", "f2025" from Runtime Context. To find companies by founder criteria, search founders first. - founders: Search for YC founders by name, work experience, educational experience, and more. The `past_experiences.employer.tags` filter contains INDUSTRY categories only (e.g., "SaaS", "Fintech", "AI") — NOT company attributes like "Unicorn" or "FAANG". To find founders from specific notable companies, use `past_experiences.employer.name` with the company name instead. The `top_company` filter (true/false) identifies founders from well-known companies but is very selective. CSV exports include separate first_name, last_name, company, link, batches, sub_batch_group, partners, and linkedin_url columns when available. The company column contains current YC company names. LinkedIn links are complete Bookface redirects; keep their query strings intact. Available filters and the most common values: batches: "W22", "S21", "W21", "W23", "S24"; degrees: "BS", "BA", "MS", "PhD", "BSc"; schools: "Stanford University", "University of California, Berkeley", "Massachusetts Institute of Technology", "Harvard University", "University of Waterloo"; partners: "Unspecified", "Gustaf", "Jared", "Brad", "Aaron"; top_company: "false", "true"; batch_groups: "W22", "S21", "W21", "W23", "S24"; active_founder: "true", "false"; former_founder: "false", "true"; fields_of_study: "Computer Science", "Economics", "Mechanical Engineering", "Computer Engineering", "Electrical Engineering"; sub_batch_group: "S21 -> S21-1", "W22 -> W22-3", "W22 -> W22-2", "S21 -> S21-2", "W22 -> W22-4"; current_location: "San Francisco, CA, USA", "New York City, NY, USA", "London, England, United Kingdom", "Los Angeles, CA, USA", "Bengaluru, KA, India"; past_experiences.title: "Founder", "Software Engineer", "Co-Founder", "Founder/CEO", "Senior Software Engineer"; current_experiences.title: "Founder", "Founder/CEO", "Founder/CTO", "Co-Founder", "Founder/COO"; past_experiences.employer.name: "Google", "Microsoft", "Amazon", "Facebook", "Y Combinator"; past_experiences.employer.tags: "Top 500 Public Tech Company by Revenue", "AI", "SaaS", "B2B", "Fintech"; current_experiences.tenure_years: "5.386301369863014", "4.810958904109589", "5.824657534246575", "0.3589041095890411", "3.816438356164384"; current_experiences.employer.name: "Y Combinator", "Pioneer Fund", "Stealth Startup", "Self-Employed", "Google"; current_experiences.employer.tags: "AI", "B2B", "SaaS", "Fintech", "Developer Tools"; current_experiences.employer.batch: "Not YC", "S21", "W22", "W21", "F26"; past_experiences.employer.headcount: "1", "2", "3", "318310", "4"; past_experiences.employer.industries: "Internet", "Computer Software", "Higher Education", "Information Technology And Services", "B2B"; current_experiences.employer.headcount: "2", "3", "5", "4", "6"; past_experiences.employer.latest_round: "IPO", "Seed", "Series Unknown", "Series A", "Series B"; current_experiences.employer.industries: "B2B", "Consumer", "Healthcare", "Fintech", "Engineering, Product and Design"; current_experiences.employer.latest_round: "Seed", "Series A", "Series B", "IPO", "Series C". Available extra_fields: active_founder, avatar_thumb, batch_groups, current_experiences.employer.batch, current_experiences.employer.company_ids, current_experiences.employer.description, current_experiences.employer.headcount, current_experiences.employer.id, current_experiences.employer.industries, current_experiences.employer.latest_round, current_experiences.employer.linkedin_url, current_experiences.employer.logo_url, current_experiences.employer.model_id, current_experiences.employer.model_type, current_experiences.employer.name, current_experiences.employer.search_path, current_experiences.employer.slug, current_experiences.employer.tags, current_experiences.end_date, current_experiences.id, current_experiences.start_date, current_experiences.tenure_years, current_experiences.title, current_location, current_region, degrees, fields_of_study, former_founder, hnid, indexed_at, objectID, past_experiences.employer.alternate_names, past_experiences.employer.batch, past_experiences.employer.description, past_experiences.employer.headcount, past_experiences.employer.id, past_experiences.employer.industries, past_experiences.employer.latest_round, past_experiences.employer.linkedin_url, past_experiences.employer.logo_url, past_experiences.employer.model_id, past_experiences.employer.model_type, past_experiences.employer.name, past_experiences.employer.search_path, past_experiences.employer.slug, past_experiences.employer.tags, past_experiences.end_date, past_experiences.id, past_experiences.start_date, past_experiences.tenure_years, past_experiences.title, schools, top_company. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Filter uses "batches" (plural), not "batch". IMPORTANT: batch values use short names like "W25", "P26" — NOT long format like "w2025", "p2026". School names must be formal ("Massachusetts Institute of Technology" not "MIT"). The current_experiences/past_experiences extra fields are verbose — only request when needed. employer.tags is industry categories only, not company attributes like "Unicorn". Result link fields in current_experiences/past_experiences are pre-formatted markdown — use them directly. The top-level link column is the founder profile, not a company link. - staff: Search YC partners, visiting partners, and software team members by name, HNID, or email. Returns their email addresses and executive assistants. Can filter by staff type. Use this when founders ask who at YC to contact, for a searchable YC staff member's email address, or who a staff member's EA is. Tips: Use for YC staff contact info and EA lookups. Query by staff name, HNID, or email. Use staff_type to filter to partner, visiting_partner, or software. Omit query unless searching within that category. - investors: Search for investors in the YC investor database. Requires investor database access. Tips: To find which companies took investment from an investor, search investors first, not companies. - investor_users: Search the InvestorUsers Algolia index for an investor contact. Search by exact email when available; otherwise use the person's full name. Results include canonical contact fields, direct LinkedIn URLs, and associated investor IDs. Do not infer an identity from ambiguous matches. Never build a /user/<id> link from a result id: most investor user profiles are hidden from founders. Link /investors/<investor_id> from investor_ids instead. Tips: Search by exact email when available; otherwise use the person's full name. Results include canonical contact fields and associated investor IDs. Do not infer an identity from ambiguous matches. Never build a /user/<id> link from a result id (most investor user profiles are hidden from founders); link /investors/<investor_id> instead. - deals: Search deals and discounts available to this user, including the YC AI Stack for eligible meetup attendees (also called credits, starter packs, or student deals). Search before answering questions about credits, current offers, or redemption; never give redemption instructions from memory. Request extra_fields: "redemption,redemption_type,details". Use only returned deal links and IDs. For button deals, offer tool:deal.redeem; for instructions deals, share the returned instructions or use tool:deal.claim to reveal them. Searches returning more than ten deals cut details and redemption short; before quoting terms, credit amounts, or redemption steps, re-read those deals with ids for the full text. Available filters and the most common values: active: "true", "false"; audience: "all_founders", "active_founders", "current_batch", "students", "yc_fellows"; deal_tags: "Dev Tools / APIs", "Other", "Business Operations", "Lead Generation", "Operations"; company_batches: "S21", "W21", "W22", "W23", "W20". Available extra_fields: active, approval_state, approved, audience, clicked_count, collection, company_batches, company_description, company_id, deal_tags, details, email, has_low_rating, hidden, high_value, last_usage, logo, num_comments, objectID, recent_redemption_count, recently_added, recently_used, redemption, redemption_type, reported_count, star_count, updated_at, used_count, website_url, weighted_rating. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Deal eligibility is already scoped to the founder, so results only include deals available to them. Do NOT add a company_batches filter to get "deals for their batch" — that filters by the batch of the company OFFERING the deal (rare), not the founder's eligibility, and will drop valid results. Filter only by query/deal_tags/audience. - meetups: Search for YC meetups and events (recruiting events, alumni dinners, hackathons, office hours, conferences, demo days, etc.). Results are filtered by the user's access: public events are visible to everyone, private events are only visible to confirmed/invited attendees and event admins. Available filters and the most common values: city: "San Francisco, CA, USA", "San Francisco, California, United States", "Healdsburg, CA 95448", "New York, NY", "Cambridge, MA"; cancelled: "false", "true"; event_type: "agenda_item", "office_hours", "batch", "college", "recruiting". Available extra_fields: cancelled, capacity, description, ends_at_unix, host, objectID, one_liner, public_location, starts_at_unix. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Use ends_at_unix numeric filter to scope to current/future meetups (e.g. ends_at_unix > now). Use starts_at_unix to scope by start date. Values are unix timestamps. Use event_type filter to narrow by type. - forum: Search forum posts and comments from the YC founder community. Use item_type filter to restrict to posts or comments. Available filters and the most common values: tags: "Startup", "Marketing", "Startups", "Hiring", "San Francisco"; channel: "general", "launch_bookface", "classifieds", "recruiting", "announcements"; item_type: "Comment", "Post"; user.name: "Google Groups Importer", "Dan Goodman", "David J. Phillips", "Haseeb Awan", "Amy Buechler"; vote_count: "0", "1", "2", "3", "4"; views_count: "0", "1", "2", "3", "4"; comment_count: "0", "1", "2", "3", "4"; parent_post_id: "55969", "76664", "66180", "39094", "84562"; filterable_date: "1484953392", "1516147860", "1517854244", "1517861104", "1484159976"; parent_comment_id: "125777", "147959", "316437", "169738", "20957"; user.company.name: "Y Combinator", "Cobbery", "Fondo", "SigNoz", "Wyndly"; user.company.batches: "W21", "S21", "W22", "W24", "W23". Available extra_fields: channel, comment_count, engagement_count, featured, indexed_at, objectID, parent_comment_id, parent_post_id, searchable_title, tags, url, user.avatar_thumb, user.company.batches, user.company.id, user.company.small_logo_thumb_url, user.id, views_count, vote_count. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Sort keys: most_recent/created_at/date = newest first; most_voted/votes/vote_count = highest vote count; most_engaged/engagement = votes + comments + views; the default (relevance) is a topical ranking. NEVER call a result "the most recent" or "the most upvoted", and never say nothing newer exists, unless THAT call used the matching sort key — relevance results are ordered by neither date nor votes. Every word in query must match, so each extra word can delete the true answer; before claiming nothing matches, re-run with the fewest distinguishing terms. To check for a literal string, send a quotes-only query with nothing else in it ("live sales coach", NOT "live sales coach" launch) — bare words alongside the phrase silently make every word optional. For broad topics, use queries with keyword variations. Read a post with ids: <post_id>, a comment with ids: comment_<id> (when item_type is Comment the id column IS the comment id), or a whole thread by reading the post with ids: <post_id> AND its comments with filters: {parent_post_id: <post_id>} (limit at least the post's comment_count) — that filter matches comments only, never the post itself; those paths return full untruncated bodies. Do not use a date sort as thread order — it is newest-first only. The posted_at column is an ISO-8601 date; the filterable_date filter takes a raw unix epoch. The web tool cannot read Bookface (login wall), and indexed bodies drop markdown link URLs, so an absent link means "not visible in the indexed text", never "there is no link". - user_manuals: Search the YC User Manual and other official YC manuals and guides. Available filters and the most common values: type: "school", "post", "investor", "employer", "non_yc_company"; agent_searchable: "true", "false". Available extra_fields: agent_searchable, displayed_attributes.parents.slug, displayed_attributes.parents.title, displayed_attributes.root_id, displayed_attributes.view_access, indexed_at, objectID, rank_five, rank_four, rank_one, rank_three, rank_two, score, search_path, shared_search_version, type. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Best first resource for questions about YC programs, policy, logistics, legal/finance, immigration, hiring, and official how-tos. Authoritative and kept up to date. Prefer this over startup_library for official or current guidance. - startup_library: Search the YC Startup Library of public talks, videos, and essays. Available filters and the most common values: type: "school", "post", "investor", "employer", "non_yc_company"; agent_searchable: "true", "false". Available extra_fields: agent_searchable, displayed_attributes.parents.slug, displayed_attributes.parents.title, displayed_attributes.root_id, displayed_attributes.view_access, indexed_at, objectID, rank_five, rank_four, rank_one, rank_three, rank_two, score, search_path, shared_search_version, type. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Historical/educational content: recorded talks, founder stories, and essays. Not actively maintained and may be dated. Use for broad learning, examples, and founder perspectives; for official or current guidance prefer user_manuals. - launches: Search and fetch YC company launches on ycombinator.com (Launch YC). Find public launches by company name, title, tagline, or content. An exact company name, company_id, or Launch YC URL also returns deleted and unpublished posts and the company's launch status when the user is YC staff or an active founder of that company. Multiple distinct queries use keyword search; do not combine them with company_id or a Launch YC URL. Use this tool instead of fetching a ycombinator.com/launches URL through the web. Note: Private launches posted to Bookface in the "Launch Bookface" channel (launch_bookface) can be found using the search_forum tool. Available filters and the most common values: company.tags: "AI", "B2B", "SaaS", "Developer Tools", "Generative AI"; company.batch: "Winter 2023", "Summer 2023", "Summer 2024", "Winter 2024", "Summer 2022"; company.industry: "B2B", "Healthcare", "Industrials", "Fintech", "Consumer". Available extra_fields: body, company.id, company.industry, company.logo, company.slug, company.url, indexed_at, objectID, slug, total_vote_count, user.avatar. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Use an exact company name, company_id, or launch_url to fetch full post copy. Exact lookups include deleted and unpublished posts for YC staff or the company's active founders and also return launch status; broad searches return public launches. - chats: Search for chats and conversations by name or participants. Use the 'public' filter to distinguish between groups and private conversations: - Groups (public chats): filter by public = true - Private conversations: filter by public = false Available filters and the most common values: public: "false", "true". Available extra_fields: created_by_yc, displayed_attributes.agent_participation_mode, displayed_attributes.created_at, displayed_attributes.created_by.admin, displayed_attributes.created_by.avatar_thumb, displayed_attributes.created_by.byline_company.active, displayed_attributes.created_by.byline_company.batch, displayed_attributes.created_by.byline_company.id, displayed_attributes.created_by.byline_company.logo, displayed_attributes.created_by.byline_company.name, displayed_attributes.created_by.byline_company.url, displayed_attributes.created_by.chat_channel_key, displayed_attributes.created_by.first_name, displayed_attributes.created_by.full_name, displayed_attributes.created_by.hnid, displayed_attributes.created_by.id, displayed_attributes.created_by.last_active_on_chat_at, displayed_attributes.created_by.last_name, displayed_attributes.created_by.short_name, displayed_attributes.created_by.yc, displayed_attributes.created_by.yc_staff, displayed_attributes.current_user_can_join, displayed_attributes.current_user_is_archived, displayed_attributes.current_user_is_member, displayed_attributes.current_user_push_muted, displayed_attributes.default_email_notification_preference, displayed_attributes.default_push_notification_preference, displayed_attributes.email_notification_preference, displayed_attributes.has_audience, displayed_attributes.hide_spam_button, displayed_attributes.id, displayed_attributes.initial_last_message.anchor, displayed_attributes.initial_last_message.chat_id, displayed_attributes.initial_last_message.client_id, displayed_attributes.initial_last_message.client_message_id, displayed_attributes.initial_last_message.client_sequence_id, displayed_attributes.initial_last_message.content, displayed_attributes.initial_last_message.content_updated_at, displayed_attributes.initial_last_message.created_at, displayed_attributes.initial_last_message.deleted, displayed_attributes.initial_last_message.id, displayed_attributes.initial_last_message.linked_entities, displayed_attributes.initial_last_message.metadata.referrer, displayed_attributes.initial_last_message.metadata.source_host, displayed_attributes.initial_last_message.open_graph_extraction, displayed_attributes.initial_last_message.reactions, displayed_attributes.initial_last_message.recipient_user_id, displayed_attributes.initial_last_message.thread_id, displayed_attributes.initial_last_message.thread_reply_count, displayed_attributes.initial_last_message.thread_reply_users, displayed_attributes.initial_last_message.type, displayed_attributes.initial_last_message.updated_at, displayed_attributes.initial_last_message.user.admin, displayed_attributes.initial_last_message.user.agent_chat_enabled, displayed_attributes.initial_last_message.user.attended_meetup_ids, displayed_attributes.initial_last_message.user.avatar_thumb, displayed_attributes.initial_last_message.user.banned_from_messages, displayed_attributes.initial_last_message.user.byline_company, displayed_attributes.initial_last_message.user.chat_channel_key, displayed_attributes.initial_last_message.user.chat_email_notification_preference, displayed_attributes.initial_last_message.user.chat_push_notification_preference, displayed_attributes.initial_last_message.user.current_location, displayed_attributes.initial_last_message.user.first_name, displayed_attributes.initial_last_message.user.full_name, displayed_attributes.initial_last_message.user.has_public_messages_access, displayed_attributes.initial_last_message.user.has_push_tokens, displayed_attributes.initial_last_message.user.hnid, displayed_attributes.initial_last_message.user.id, displayed_attributes.initial_last_message.user.last_active_on_chat_at, displayed_attributes.initial_last_message.user.last_name, displayed_attributes.initial_last_message.user.linkedin_url, displayed_attributes.initial_last_message.user.short_name, displayed_attributes.initial_last_message.user.startup_school_speaker_questions_enabled, displayed_attributes.initial_last_message.user.url, displayed_attributes.initial_last_message.user.yc, displayed_attributes.initial_last_message.user.yc_staff, displayed_attributes.initial_last_message.user_targets, displayed_attributes.initial_last_message.version_number, displayed_attributes.initial_message_count, displayed_attributes.initial_show_admin_banner, displayed_attributes.is_dm, displayed_attributes.is_locked, displayed_attributes.join_link, displayed_attributes.last_active_at, displayed_attributes.last_read_message_id, displayed_attributes.marked_as_spam, displayed_attributes.name, displayed_attributes.path, displayed_attributes.public_visibility_removal_count, displayed_attributes.push_notification_preference, displayed_attributes.resolved_default_email_notification_preference, displayed_attributes.resolved_default_push_notification_preference, displayed_attributes.restrict_add_members, displayed_attributes.should_show_add_to_crm, displayed_attributes.show_join_messages, displayed_attributes.show_member_list, displayed_attributes.subtitle, displayed_attributes.summary, displayed_attributes.system_managed, displayed_attributes.type, displayed_attributes.updated_at, displayed_attributes.user_count, displayed_attributes.visibility, displayed_attributes.waterline_message_id, indexed_at, objectID, updated_at, user_ids. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. - alumni_groups: Search public alumni groups by group name or description. Results link to the backing chat for each group. Available extra_fields: category, objectID. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. Tips: Use for alumni group discovery. Results link to the backing chat. - jobs: Search for jobs at YC companies on Work at a Startup. Find jobs by title, company, skills, location, or sector. Available filters and the most common values: id: "93174", "93184", "93192", "93198", "93199"; role: "eng", "operations", "sales", "marketing", "product"; remote: "no", "yes", "only"; eng_type: "fs", "be", "ml", "fe", "devops"; job_type: "fulltime", "intern", "contract", "cofounder"; has_equity: "false", "true"; has_salary: "true", "false"; design_type: "web", "product", "ui_ux", "brand_graphic", "mobile"; science_type: "research", "health", "biotech", "bio", "process"; min_experience: "3", "0", "1", "6", "5"; recruiting_type: "recruiter", "fullcycle", "operations", "lead", "sourcer"; us_visa_required: "yes", "none", "possible"; company_team_size: "500", "3", "10", "5", "2"; company_waas_stage: "seed", "unannouced", "series_a", "growth", "scale"; locations_for_search: "US", "CA, US", "San Francisco, CA, US", "NY, US", "New York, NY, US"; company_parent_sector: "B2B Software and Services", "Healthcare", "Industrials", "Financial Technology and Services", "Consumer"; has_interview_process: "false", "true"; company_highlight_black: "false", "true"; company_highlight_women: "false", "true"; company_highlight_latinx: "false", "true". Available extra_fields: company_child_sector, company_created_at, company_description, company_highlight_black, company_highlight_latinx, company_highlight_women, company_hiring_description, company_id, company_team_size, company_waas_activity_score, company_waas_stage, company_website, created_at, description, design_type, eng_type, has_equity, has_interview_process, has_salary, min_experience, objectID, recruiting_type, role, science_type, us_visa_required. You can fetch specific records by ID using the 'ids' parameter (mutually exclusive with query/queries/filters/sort/optional_keywords). If you need to use a range, use the format <facet name>: X TO Y. - routes: Required before answering where to find a Bookface page or feature, or giving its URL or relative path. Returns pages the user can access, including destinations outside the navbar, with their names and URLs. Use exact URLs and paths returned by tools in this conversation. Never guess or construct routes, including copying unverified URLs from earlier assistant replies. If no matching route is found, say so without inventing a link. - follows: List the current user's followers or the users they follow. Returns user IDs and basic info that can be joined with search_founder_nav_users results. Use direction "followers" to see who follows the current user, or "following" to see who the current user follows.
The description explains the capability, when to use it, and what to expect.
Inputs91/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
entity
What to search. Each entity searches a different index.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Search keywords (space-separated). Not required when using filters.
Clear enough to supply this argument.
queries
Alternative keyword queries (max 8 distinct queries including query). Matches from any query are combined and deduplicated; relevance searches interleave query rankings, and sorted searches merge into one list in the requested sort order. Prefer this for synonyms, related phrases, and keyword variants instead of making repeated search calls that only change query text.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
staff_type
For staff entity: filter to partner, visiting_partner, or software.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Max results to return (default 10, max 200; employers: 1 to 25). Use 0 for count-only queries except employers, which do not support count-only. Ignored for CSV exports (attach_csv=true), which return the matching records up to a per-entity export limit or the file-size cap.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
page
Page number for pagination (0-indexed)
Clear enough to supply this argument.
optional_keywords
Space-separated keywords that boost results when matched but are not required.
Clear enough to supply this argument.
ids
Comma-separated IDs to fetch directly. Cannot be combined with query/queries/filters/sort. Use to re-read specific records in full; accepted id forms vary by entity (see that entity's tips).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
group_counts_by
Return result counts grouped by this facet instead of individual results.
Clear enough to supply this argument.
extra_fields
Comma-separated list of additional fields to include (see available_extra_fields in response)
Clear enough to supply this argument.
attach_csv
Set true when the user asks to export or download Algolia-backed search results as a CSV attachment. Prefer this over csv.create for search result exports. The export returns the matching records up to a per-entity limit; the limit parameter and paging are ignored for exports — narrow the query/filters to target specific records.
Clear enough to supply this argument.
csv_filename
Optional filename for the CSV attachment. Used only when attach_csv is true.
Clear enough to supply this argument.
filters
Filter object where keys are filter names and values are strings or arrays of strings (OR within filter). Batch filters use SHORT names (e.g. "W25", "P26"), not long format ("w2025", "p2026"). Filter values must match exactly — "Harvard" won't match "Harvard University". Use limit: 0 to probe available_filters and filter_value_examples before filtering on unfamiliar values.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
sort
Sort order. Available options vary by entity (see response).
Clear enough to supply this argument.
poc
For employers: contact name, email, or LinkedIn profile URL. Combine with query to narrow company matches.
Clear enough to supply this argument.
direction
For follows entity: "followers" or "following"
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
section
For routes entity: filter by section name
Clear enough to supply this argument.
company_id
For launches: exact company lookup, including authorized deleted and unpublished posts
Clear enough to supply this argument.
launch_url
For launches: exact ycombinator.com/launches URL lookup
Clear enough to supply this argument.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared