Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GovAuctions Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgovauctions.app%2Fgovauctions" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgovauctions.app%2Fgovauctions" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with GovAuctions Data API.
Search live government-surplus auction listings by facts
Value a described item against sold-price comps across six markets
Read month-by-month median sale price trends for an item
Score a live lot's resale potential with the Flip Score signal
Pull the individual archived sales behind a valuation
GET STARTED
Subscribe to webhooks that push when new lots appear
Patterns agents use GovAuctions Data API for, with concrete tasks.
★ Agent-driven resale sourcing
An AI agent can source resale inventory through GovAuctions by searching live surplus listings, valuing each candidate against sold-price comps, and reading its Flip Score before deciding to bid elsewhere. Because listings carry facts rather than images, the data is compact enough for an agent to scan at scale. Connected through Jentic, the agent calls only the read and valuation operations it needs.
Search live listings for a category, value the top candidate against sold-price comps, and read its Flip Score to decide whether to pursue it
Item valuation and comps
Resellers and analysts need a defensible resale value for an item. GovAuctions returns a sold-price range from the full surplus market and the individual archived sales behind it, so a valuation can be audited. The batch comps operation values multiple items in one request, each counted against the plan's valuation allowance.
Value up to ten described items in one batch request and return each item's sold-price range
New-lot monitoring
Buyers want to react the moment a relevant lot is listed. GovAuctions pushes new lots to a webhook subscription, so an agent can trigger a valuation and alert workflow without polling the listings endpoint. Coverage and usage endpoints let the agent confirm what data is available and how much budget remains.
Create a webhook subscription for a category and value each new lot it reports
14 endpoints — the govauctions data api returns structured government-surplus auction data: live listings from sanctioned federal sources, sold-price comps, and the govauctions flip score resale signal.
METHOD
PATH
DESCRIPTION
/listings
Search live listings
/listings/{id}
Get one live listing by id
/comps
Sold-price range for a described item
/comps/batch
Value multiple items in one request
/comps/trend
Monthly median sale price for an item
/flip-score
Flip Score resale signal for a live lot
/export
Bulk CSV export
/listings
Search live listings
/listings/{id}
Get one live listing by id
/comps
Sold-price range for a described item
/comps/batch
Value multiple items in one request
/comps/trend
Monthly median sale price for an item
/flip-score
Flip Score resale signal for a live lot
/export
Bulk CSV export
What agents get from Jentic-routed access to this vendor.
Setup
Wiring GovAuctions by hand means handling its Bearer token or x-api-key header and tracking two separate budgets, the call budget and the valuation allowance, yourself. Through Jentic you install once, import GovAuctions from the API Directory, store the key once, and your agent calls it.
Permission scoping
GovAuctions carries search filters and item descriptions in the query and body, so a rule bounds which operations your agent may call rather than which listing. You choose the operations it may call, so the webhook-delete operation is not included unless you add it.
Credential isolation
Your GovAuctions key 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.
Intent-based discovery
Agents search Jentic by intent such as 'search surplus listings' or 'value an item', and Jentic returns the matching GovAuctions operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GovAuctions Data API through Jentic.
What authentication does the GovAuctions Data API use?
GovAuctions authenticates with your API key as a Bearer token in the Authorization header, or as the x-api-key header, per its OpenAPI spec. The sources listing is public, while the rest require the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.
Can I value a described item with the GovAuctions Data API?
Yes. The comps operation returns a sold-price range for a described item from the full surplus market, the trend operation returns its monthly median price, and the batch operation values several items in one request. Each valuation counts against your plan's valuation allowance.
What are the rate limits for the GovAuctions Data API?
Instead of fixed per-second limits, each plan carries a total call budget and a smaller valuation allowance, and the usage endpoint reports what remains for the month. Check https://govauctions.app for current plan budgets.
How do I search listings and value an item with the GovAuctions Data API through Jentic?
Search Jentic for 'search surplus auction listings' and it returns the GovAuctions listing-search operation with its input schema, then search 'value an item' for the comps operation. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import GovAuctions from the API Directory, and store your key once. 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 GovAuctions?
Yes. Write a rule that allows only the listing-search and valuation read operations, so the agent can research and value lots but cannot create or delete webhook subscriptions, and every call it makes is logged.
Is there a GovAuctions MCP server?
You don't need an MCP server to connect your agent to GovAuctions. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.
For Agents
Lets an AI agent search live government-surplus auction listings, value items against sold-price comps, and read Flip Score resale signals across six markets.
Use for: Search for live GSA surplus listings in a category, Get the sold-price range for a described item, Check whether a live lot is worth reselling, Retrieve the archived sales behind a valuation
Not supported: Does not handle placing bids, processing payments, or arranging shipping. Use for government-surplus auction data and resale valuation only.
The GovAuctions Data API returns structured government-surplus auction data: live listings from sanctioned federal sources, sold-price comps, and the GovAuctions Flip Score resale signal. Comps cover the full surplus market across the US, UK, CA, AU, DE, and FR, and every plan carries a total call budget plus a smaller valuation allowance. The API also exposes coverage, usage, webhook subscriptions, and bulk CSV export.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>