canonical: https://jentic.com/apis/fieldrobin.com/fieldrobin

# FieldRobin Public API

The FieldRobin Public API exposes FieldRobin's public, unauthenticated content and agent-commerce surfaces. It serves published blog posts and their categories, a public directory of businesses with detail pages, and cached active government contract opportunities with NAICS and PSC filter options. A set of agent endpoints returns an A2A agent card, handles a minimal A2A message, describes the UCP service entry point, and starts a UCP content checkout handoff. No credential is required, and authenticated application, account, administrative, and webhook endpoints are intentionally excluded from this surface.

## For AI agents

Read FieldRobin's public data through agent-friendly endpoints: published blog posts, a business directory with detail pages, cached government contract opportunities with NAICS and PSC filters, and A2A and UCP agent-commerce entry points.

## Scope

Does not handle account, admin, webhook, or tokenized operations, which are excluded from this public surface. Use for reading FieldRobin's public blog, directory, and government-opportunity data and its agent-commerce entry points only.

## Capabilities

- List published blog posts and their categories via GET `/v1/blog/posts` and GET `/v1/blog/posts/categories`
- Read a single blog post by slug via GET `/v1/blog/posts/{slug}`
- List published directory businesses and read a listing by slug via GET `/v1/directory/public` and GET `/v1/directory/public/{slug}`
- List cached active government contract opportunities with NAICS and PSC filter options via GET `/v1/government-opportunities/public` and its filter-options endpoint
- View a government opportunity by SEO slug or legacy notice id via GET `/v1/government-opportunities/public/{identifier}`
- Fetch the FieldRobin A2A agent card and handle an A2A message via GET and POST `/v1/agent/a2a`
- Start a UCP content checkout handoff via POST `/v1/agent/ucp/checkout`

## Use cases

### AI agent public-data reader

An AI agent reads FieldRobin's public content and commerce surfaces without any sign-in step. Through Jentic it discovers the endpoints, pulls directory listings and government opportunities, and can start a UCP checkout handoff when the workflow calls for it. Because the surface is public, there is no secret for the agent to hold.

Example prompt: Search Jentic for 'list active government opportunities', call GET `/v1/government-opportunities/public`, then read GET `/v1/government-opportunities/public/{identifier}` for the ones worth pursuing

### Government contract discovery

Teams chasing public-sector work need to find active opportunities and narrow them by code. The FieldRobin Public API lists cached active government opportunities and exposes NAICS and PSC filter options, then returns a single opportunity by its SEO slug or legacy notice identifier. A sitemap endpoint lists active contract slugs for indexing.

Example prompt: Call GET `/v1/government-opportunities/public/filter-options` to get NAICS and PSC options, then GET `/v1/government-opportunities/public` filtered to the codes the business qualifies for

### Business directory lookup

A directory experience lists published businesses and drills into any one by slug. The FieldRobin Public API returns the directory list, the filter options behind it, and a detail page per listing, so a frontend or agent can browse and resolve a specific business. The data is public, so it can be fetched without an account.

Example prompt: Call GET `/v1/directory/public` to list businesses, read GET `/v1/directory/public/filter-options` for facets, then GET `/v1/directory/public/{slug}` for a listing's detail

### Blog content syndication

Marketing and content tools pull FieldRobin's published posts to syndicate or index them. The API lists posts and their categories, returns a post by slug, and publishes a blog sitemap for crawlers, so a content pipeline can mirror the blog cleanly. Media assets stream from a fallback endpoint when no CDN URL is present.

Example prompt: Call GET `/v1/blog/posts` to list posts, then GET `/v1/blog/posts/{slug}` for each one you want to syndicate

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/blog/posts` | List published blog posts |
| GET | `/v1/blog/posts/{slug}` | Get a published blog post by slug |
| GET | `/v1/government-opportunities/public` | List cached active government opportunities |
| GET | `/v1/government-opportunities/public/{identifier}` | View a government opportunity by slug or notice id |
| GET | `/v1/directory/public` | List published directory businesses |
| GET | `/v1/directory/public/{slug}` | Get a directory listing detail |
| GET | `/v1/agent/a2a` | Return the FieldRobin A2A agent card |
| POST | `/v1/agent/ucp/checkout` | Start a UCP content checkout handoff |

## Key resources

- **Blog** — List published posts and categories, read a post by slug, and fetch the blog sitemap and media assets
- **Government opportunities** — List cached active opportunities with NAICS and PSC filters, read one by slug or notice id, and fetch the sitemap
- **Directory** — List published directory businesses, read filter options, and fetch a listing by slug
- **Agent commerce** — Return the A2A agent card, handle an A2A message, describe the UCP entry point, and start a UCP content checkout

## 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:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 53 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 41 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 45 / 100
- **View full report:** https://jentic.com/apis/fieldrobin.com/fieldrobin/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the FieldRobin Public API by hand means tracking its public endpoints and the A2A and UCP agent-commerce handshakes yourself. Through Jentic you install once, import FieldRobin from the API Directory, and your agent calls it, with no credential to manage because the surface is public.
- **Permission scoping:** Every FieldRobin Public endpoint is public and read-oriented, so a rule simply limits which operations your agent may call: the blog, directory, and government-opportunity reads, or the A2A and UCP agent-commerce entry points. You choose the operations it may call, so you can keep the checkout handoff out unless you want the agent to start one.
- **Credential handling:** The FieldRobin Public API needs no credential, so there is nothing for Jentic to store or inject: your agent calls the public endpoints directly. Your rules still decide which of those operations it may use.
- **Discovery method:** Agents search Jentic by intent such as 'list active government opportunities' or 'read a directory business', and Jentic returns the matching FieldRobin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Licitalab** — Public procurement and tender data, the same discovery function for government opportunities in another market
- **Jungle Scout API** — Market and product data that pairs with FieldRobin's business directory for commercial research
- **MojePanstwo API** — Public-institution and registry data, another source of company and government-sector records

## FAQ

### What authentication does the FieldRobin Public API use?

The FieldRobin Public API requires no authentication; its endpoints are public and unauthenticated. Authenticated application, account, administrative, webhook, and tokenized endpoints are intentionally excluded from this public surface, so an agent can read the data directly.

### Can I find active government contract opportunities with the FieldRobin Public API?

Yes. Call GET `/v1/government-opportunities/public` for the cached active opportunities, narrow them with the NAICS and PSC options from GET `/v1/government-opportunities/public/filter-options`, and read a single one with GET `/v1/government-opportunities/public/{identifier}` by its SEO slug or legacy notice id.

### Can the FieldRobin Public API return business directory listings?

Yes. GET `/v1/directory/public` lists published directory businesses, GET `/v1/directory/public/filter-options` returns the facets to narrow them, and GET `/v1/directory/public/{slug}` returns a single listing's detail. All of it is public data, so no account is needed.

### What are the rate limits for the FieldRobin Public API?

The OpenAPI spec does not specify rate limits for the FieldRobin Public API. Check the FieldRobin documentation for current limits, cache stable responses like the blog and directory sitemaps, and have your agent back off when the API signals that it is being throttled.

### How do I read government opportunities through Jentic?

Search Jentic for 'list active government opportunities' to load the FieldRobin operation with its input schema, call GET `/v1/government-opportunities/public`, and drill in with GET `/v1/government-opportunities/public/{identifier}.` To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the FieldRobin Public API?

Yes. Because you run Jentic One yourself, you decide which FieldRobin operations the agent may call. You can allow only the blog, directory, and government-opportunity reads and leave out the UCP checkout handoff unless you want the agent to start one, and every call it makes is logged.