AutoRFP.ai Agent API
71
AI ReadinessAI-Aware (A-)71/100
Official vendor OpenAPI document · agent-readyProductivityCollaborationoauth215 EndpointsREST
For Agents
Discover an AutoRFP.ai workspace and read its projects, requirements, and approved RFP content through an OAuth-scoped, read-only endpoint. Public discovery endpoints need no credential.
Use for: I want to discover the AutoRFP.ai agent resources, Read the public site identity for a workspace, Find the agent registration instructions, Search approved content to answer an RFP question
Not supported: Does not draft, submit, or edit proposal responses, and does not place or price orders. Use for discovering AutoRFP.ai resources and reading RFP projects, requirements, and approved content only.
The AutoRFP.ai Agent API provides discovery and read access to an AutoRFP.ai workspace for AI agents. Public discovery endpoints return agent resources, site identity, resource listings, and the OpenAPI and Swagger documents without credentials. An authenticated Model Context Protocol endpoint, scoped by OAuth, returns the workspace's tag vocabulary, projects and their requirements, and approved answer content and its usage, always limited to what the authorized user can see.
Install Jentic One Beta
Connect the AutoRFP.ai Agent API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AutoRFP.ai Agent 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.
1
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%2Fautorfp.ai%2Fautorfp" | sh2
Step 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%2Fautorfp.ai%2Fautorfp" | 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.
Capabilities
What an agent can do with AutoRFP.ai Agent API.
Discover AutoRFP.ai agent resources, site identity, and public resource listings
Read the OpenAPI and Swagger documents for the API
Discover the Model Context Protocol server and its capability catalogs
Read a workspace's projects and their requirements through the authenticated endpoint
Search and read approved RFP answer content and its usage, scoped to the authorized user
Use Cases
Patterns agents use AutoRFP.ai Agent API for, with concrete tasks.
★ AI Agent RFP Integration via Jentic
An agent that drafts or researches RFP responses can reach an AutoRFP.ai workspace through Jentic without handling the OAuth dance or the discovery endpoints. The agent searches by intent, authorizes once, and reads the workspace's projects, requirements, and approved content as structured data. This fits proposal-assistant agents that need grounded, approved answer material rather than invented text.
Search Jentic for 'search approved content', authorize with OAuth, and read the matching approved answers for an RFP question
RFP Content Retrieval
Pull approved answer content from a workspace to ground an RFP response. The authenticated endpoint, with the content read scope, searches and returns approved content and its usage, so a proposal agent reuses vetted material instead of generating unverified claims. Access is limited to what the authorized user can see.
Call POST /mcp with a content read request to search approved RFP content for a topic
Workspace and Resource Discovery
Discover what an AutoRFP.ai workspace exposes before calling it. The public endpoints return agent resources, site identity, resource listings, and the machine-readable OpenAPI document, so an agent can orient itself and register without any credential.
Call GET /api/v1/resources.json to list the public API resources, then GET /api/v1/site.json for the site identity
Requirement Reading for Proposals
Read a project's requirements so an agent can structure a response around them. With the projects read scope, the authenticated endpoint returns the workspace's projects and the requirements inside them, giving the agent the questions to answer before it retrieves content.
Call POST /mcp to read a project's requirements before drafting a response
Key Endpoints
15 endpoints — the autorfp.
METHOD
PATH
DESCRIPTION
GET
/api/agent-resources.json
List AutoRFP.ai agent resources
GET
/api/v1/site.json
Read public site identity
GET
/api/v1/resources.json
List public API resources
GET
/openapi.json
Download the OpenAPI document
GET
/.well-known/mcp.json
Discover the Model Context Protocol server
GET
/.well-known/agent-skills/index.json
Read the agent-skills discovery index
GET
/auth.md
Read agent registration instructions
POST
/mcp
Send an authenticated Model Context Protocol request
GET
/api/agent-resources.json
List AutoRFP.ai agent resources
GET
/api/v1/site.json
Read public site identity
GET
/api/v1/resources.json
List public API resources
GET
/openapi.json
Download the OpenAPI document
GET
/.well-known/mcp.json
Discover the Model Context Protocol server
GET
/.well-known/agent-skills/index.json
Read the agent-skills discovery index
GET
/auth.md
Read agent registration instructions
POST
/mcp
Send an authenticated Model Context Protocol request
Jentic AI Readiness Score
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.
A
AutoRFP.ai Agent API
- AI-Aware (A-)71/100
100
Foundational Compliance59
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability90
Security78
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
3%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
33%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
32%
Description Coverage
Coverage of descriptions across API elements.
27%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
48%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
90
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
90%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
78
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
78%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AutoRFP.ai API by hand means registering an OAuth client with PKCE, requesting the read scopes you need, and calling the discovery endpoints before the content gateway. Through Jentic you install once, import AutoRFP.ai from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
AutoRFP.ai gates its read access behind OAuth scopes for tags, projects, and content, so a rule can grant your agent only the scopes and operations you choose. You decide which reads it may perform, so it can search content without reaching anything the scopes do not cover.
Credential isolation
Your AutoRFP.ai OAuth credential 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 'read a project's requirements' or 'search approved content', and Jentic returns the matching AutoRFP.ai operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AutoRFP.ai Agent API through Jentic.
Is there an AutoRFP.ai MCP server?
Yes, AutoRFP.ai publishes a read-only Model Context Protocol server, and you can also connect it directly through Jentic from the API Directory: import it, authorize once with OAuth, and your agent calls the discovery and content operations without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the AutoRFP.ai API?
Yes. The API is read-only and gated by OAuth scopes, so you grant your agent just the scopes it needs, such as reading projects and content, and it can search and read while anything outside those scopes is refused. Every call is logged by your self-hosted instance.
What authentication does the AutoRFP.ai API use?
The authenticated endpoint uses OAuth 2.0 authorization code with PKCE and read scopes for tags, projects, and content, per its OpenAPI spec; the discovery endpoints are public and need no credential. Through Jentic the OAuth credential is stored encrypted by your own Jentic One instance and injected at call time.
Can I read RFP project requirements with the AutoRFP.ai API?
Yes. With the projects read scope, the authenticated endpoint returns a workspace's projects and their requirements, and the content read scope returns approved answer content and its usage. Access stays limited to what the authorized user can see.
What are the rate limits for the AutoRFP.ai API?
The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://autorfp.ai for current limits.
How do I read a project's requirements with the AutoRFP.ai API through Jentic?
Search Jentic for 'read a project's requirements' and it returns the AutoRFP.ai operation with its input schema; authorize once with OAuth and the agent reads the requirements as structured data. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED