BoundaryAI API
51
AI ReadinessFoundational (C-)51/100
Official vendor OpenAPI document · agent-readyProductivityForms Surveysbearer, apiKey949 EndpointsREST
For Agents
Create and AI-generate surveys, collect responses, and analyze feedback for a BoundaryAI organization, then build and distribute reports. Authenticates with a bearer API key in the Authorization header.
Use for: Create a new customer feedback survey, Generate a survey from a short description with AI, Collect responses for an embedded survey, Summarize the responses to a survey
Not supported: Does not handle CRM contact management, email marketing campaigns, or web traffic analytics. Use for creating surveys, collecting responses, and analyzing feedback only.
The BoundaryAI API builds customer surveys, collects their responses, and turns the results into analysis, flags, and reports for a feedback and market-research platform. You can author a survey by hand or generate one from a short description, serve it through embedded and shareable survey flows, then read back responses and run analysis that drafts replies and raises flags. Survey series track the same study over time with evolution buckets and monitors, and reports can be scheduled and distributed to named recipients.
Install Jentic One Beta
Connect the BoundaryAI API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BoundaryAI 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%2Fboundary-ai.com%2Fboundary-ai" | 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%2Fboundary-ai.com%2Fboundary-ai" | 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 BoundaryAI API.
Create customer surveys by hand or generate them from a short prompt with AI
Collect survey responses through embedded, shareable, and partial-save flows
Analyze responses to raise flags, summarize themes, and draft replies
Build, schedule, and distribute reports to named recipients
Track a survey series over time with evolution buckets and monitors
Manage API keys, organizations, and native data connectors
Use Cases
Patterns agents use BoundaryAI API for, with concrete tasks.
★ Agent-Driven Survey Operations
An AI agent connected through Jentic creates a survey for a BoundaryAI organization, publishes it, and then reads back the collected responses so a feedback program runs without a person operating the dashboard. Because the analysis operations return structured flags and summaries, the agent can act on the findings rather than reading raw responses one by one.
Create a post-purchase survey for my store, publish it, and summarize the first batch of responses
AI-Generated Survey Design
A product team turns a short brief into a ready survey by calling the AI survey generation operation, which drafts questions from a description, then refines the draft with the standard editing operations. This shortens the gap between deciding to measure something and fielding a usable questionnaire.
Generate a five-question customer satisfaction survey from the brief 'measure delivery speed and support quality'
Automated Response Analysis
An analyst pipeline collects survey responses and runs the analysis operations to raise flags on concerning answers and draft replies, so a human reviews conclusions instead of combing through every response. Flags can feed monitors on a survey series to watch a metric over successive waves.
Analyze the latest survey wave, raise flags on negative delivery feedback, and draft a reply for each flagged response
Scheduled Report Distribution
An operations team schedules a report on a survey series and distributes it to a recipient list, so stakeholders receive results on a cadence without anyone exporting data manually. Report subscriptions add an approval step before a run is sent.
Schedule a weekly report for this survey series and add two recipients to its distribution list
Key Endpoints
949 endpoints — the boundaryai api builds customer surveys, collects their responses, and turns the results into analysis, flags, and reports for a feedback and market-research platform.
METHOD
PATH
DESCRIPTION
GET
/surveys
List surveys
POST
/surveys
Create a survey
POST
/surveys/ai-generate
Generate a survey from a prompt with AI
GET
/surveyseries/{org_id}
List survey series for an organization
POST
/chat/{org_id}/ask
Ask the analytics assistant a question
GET
/api/keys
List API keys
POST
/api/keys
Create an API key
GET
/surveys
List surveys
POST
/surveys
Create a survey
POST
/surveys/ai-generate
Generate a survey from a prompt with AI
GET
/surveyseries/{org_id}
List survey series for an organization
POST
/chat/{org_id}/ask
Ask the analytics assistant a question
GET
/api/keys
List API keys
POST
/api/keys
Create an API key
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.
B
BoundaryAI API
- Foundational (C-)51/100
46
Foundational Compliance60
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience43
Agent Usability59
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
46
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
83%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
60
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
80%
Example Validity
Percentage of examples that conform to their schemas.
60%
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.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
46%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
59
Security
Trust, risk posture, and security compliance.
Grade: C+Signals: 1
59%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
67%
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 BoundaryAI API by hand means managing its bearer API key auth, picking the survey, analysis, and reporting routes you need out of a large surface, and handling pagination yourself. Through Jentic you install once, import BoundaryAI from the API Directory, store the token once, and your agent calls it.
Permission scoping
BoundaryAI puts the organization id in the URL path for many routes, such as its survey-series and chat routes, so a rule can pin your agent to one organization's data. You choose which operations it may call, so write actions like deleting surveys or rotating API keys are not included unless you add them.
Credential isolation
Your BoundaryAI API 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 'create a customer survey' or 'summarize survey responses', and Jentic returns the matching BoundaryAI operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BoundaryAI API through Jentic.
Is there a BoundaryAI MCP server?
You don't need an MCP server to give your agent the BoundaryAI API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can create surveys and read responses straight away, with no extra server to run and no tool definitions loaded into the agent's context.
Can I limit what my agent is allowed to do with the BoundaryAI API?
Yes. Write a rule that allows only the survey-read and response-read operations for one organization, so the agent can pull survey results and nothing else, and every call it makes is logged. If you later want it to create surveys as well, you add that one operation to the rule.
What authentication does the BoundaryAI API use?
The BoundaryAI API authenticates with a bearer API key passed in the Authorization header per its OpenAPI spec, while the dashboard web app signs in with a Clerk-issued session token. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.
Can I generate a survey with AI using the BoundaryAI API?
Yes. The API includes an AI survey generation operation that drafts a questionnaire from a short description, alongside the standard create-survey operation, so an agent can turn a prompt like 'a five-question post-purchase survey' into a ready draft it can then edit.
What are the rate limits for the BoundaryAI API?
Each BoundaryAI API key carries its own per-minute rate limit set on the key, as described in the OpenAPI spec; the spec does not publish a single fixed number for every account. For the limit that applies to your key, check the key's settings in the BoundaryAI dashboard under Integrations Hub.
How do I create a survey with the BoundaryAI API through Jentic?
Import the BoundaryAI API from the Jentic API Directory, then have your agent issue a request such as 'create a post-purchase survey for my store'. Jentic matches the intent to the create-survey operation and returns its input schema so the agent builds a valid request, with your stored API key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED