canonical: https://jentic.com/apis/guildai.co/guildai # Guildai GUILD Public Opportunity Feed API The GUILD Public Opportunity Feed API returns up to five GUILD-curated public and outsourced manufacturing opportunities to approved media and channel partner backends. Each opportunity carries a rank, the week it was curated, a solicitation number, an optional national stock number, an item name, a quantity, an estimated supplier manufacturing value in USD, a lead time, required certifications, and a public engagement URL. The feed is read-only and backend-only: the GUILD-issued token is meant to be used from partner infrastructure, not from a browser. ## For AI agents Retrieve up to five ranked, GUILD-curated manufacturing and procurement opportunities, each with a solicitation number, quantity, estimated supplier value, required certifications, and a public engagement URL. ## Scope Does not handle submitting bids, placing orders, or managing contracts. Use for reading curated public manufacturing opportunities only. ## Capabilities - Fetch up to five ranked public manufacturing opportunities curated by GUILD - Read each opportunity's solicitation number and optional national stock number - Surface estimated supplier manufacturing value, quantity, and lead time for every pick - Pass through required certifications and the public engagement URL to a partner front end - Respect the server cache directive returned with the feed response ## Use cases ### Partner Opportunity Widget A media or channel partner displays GUILD-curated manufacturing opportunities on its own site. The agent calls the opportunity feed from the partner backend, reads the ranked picks, and renders each one with its solicitation number, quantity, estimated supplier manufacturing value, and engagement URL. Because the feed returns at most five curated picks, the partner shows a tight, pre-vetted shortlist rather than an unfiltered firehose. Example prompt: Call the GUILD opportunity feed and return the rank-1 opportunity's solicitation number, quantity, and estimated supplier manufacturing value ### Manufacturer Matching A sourcing agent matches the certifications it holds against the required certifications on each opportunity before deciding which to pursue. The feed exposes a required-certifications list and a lead time per opportunity, so the agent can filter to picks whose requirements a manufacturer can actually meet and rank the rest by estimated supplier manufacturing value. Example prompt: Fetch the feed and return only opportunities whose required certifications include ISO 9001, sorted by estimated supplier manufacturing value ### New Opportunity Monitor An agent polls the GUILD feed on the cadence agreed with the integration and alerts an operator when a new week's curated picks appear. The response carries a week-start date per opportunity and a server cache directive, so the agent can respect the no-store signal and detect when the ranked set has changed. Example prompt: Poll the opportunity feed, compare the week-start dates against the last seen set, and alert when a new curated opportunity is published ## Key resources - **Opportunity Feed** — A single read operation returning up to five ranked, GUILD-curated manufacturing opportunities with their solicitation details, values, certifications, and engagement URL ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 50 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/guildai.co/guildai/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the GUILD feed by hand means handling its backend-only bearer token, keeping that token off the browser, and backing off cleanly on a 429. Through Jentic you install once, import the GUILD opportunity feed from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The GUILD API has one read operation and no write surface, so a rule bounds your agent to that single feed call for the integration client the token represents. You choose that it may read opportunities and nothing more, because there are no destructive operations to add. - **Credential handling:** Your GUILD integration token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get curated manufacturing opportunities', and Jentic returns the GUILD feed operation with its response schema so the agent reads the ranked picks without browsing the reference docs. ## Related APIs - **Crunchbase** — Crunchbase returns company, funding, and firmographic data rather than curated manufacturing opportunities. - **Data.gov** — Data.gov exposes broad US government open datasets that can add context to a curated opportunity. - **USA.gov** — USA.gov provides US government information and service directories to supplement opportunity data. ## FAQ ### What authentication does the GUILD Public Opportunity Feed API use? Per its OpenAPI spec, the GUILD API authenticates with a bearer token: a GUILD-issued integration token passed in the Authorization header. The token is backend-only and meant to be used from partner infrastructure, so through Jentic it is stored by your own self-hosted instance and injected when the agent calls the feed, never printed into the agent's prompt or logs. ### Can I retrieve the national stock number for an opportunity with the GUILD API? Yes, when GUILD has one for that pick. Each opportunity in the feed carries an optional national stock number alongside its solicitation number, item name, quantity, estimated supplier manufacturing value, lead time, and required certifications. The field can be null, so an agent should treat it as present-when-available rather than guaranteed. ### What are the rate limits for the GUILD Public Opportunity Feed API? The OpenAPI spec does not publish a numeric rate limit. It does define a 429 response for requests that exceed the agreed integration pattern, so an agent should back off when it sees one and poll on the cadence agreed with GUILD. For current limits, check the GUILD documentation at https://docs.guildai.co. ### Can I limit what my agent is allowed to do with the GUILD API? Yes. The GUILD API exposes a single read operation, so a rule can allow your agent exactly that one feed call and nothing else, and every call it makes is logged. There is no write or delete surface to restrict, which keeps the blast radius to reading curated opportunities for the one integration client the token belongs to. ### Is there a GUILD MCP server? You do not need an MCP server to give your agent the GUILD API. Jentic connects it directly from the Jentic API Directory: import the GUILD opportunity feed, store your integration token once, and your agent calls it on demand without loading a separate server's tool definitions into its context. ### How do I read the GUILD opportunity feed through Jentic? Search Jentic by intent such as 'get curated manufacturing opportunities', and Jentic returns the GUILD feed operation with its response schema so the agent reads the ranked picks directly. To run it on your own infrastructure, install Jentic One from its GitHub repo with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the GUILD API from the directory.