Community OpenAPI document · agent-readyStorageDocument Managementbearer22 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage rental property units and tenancies, issue inspection scan links, upload scan videos, and retrieve the AI-generated inspection reports. Authenticates with a bearer token.
Use for: Create a new property unit, Generate a scan link for a tenant to submit an inspection, List all inspection reports for a unit, Get the details of a specific report
Not supported: Does not handle rent collection, payment processing, or property listing and marketing. Use for property unit, tenancy, and inspection report management only.
The Paraspot API manages rental property units, tenancies, and the AI-generated inspection reports produced from tenant video scans. It registers and updates units and the properties that group them, issues scan links that tenants use to submit an inspection, and returns the resulting reports with their past scans, inspection type, and resident data. Media operations upload scan videos and mint presigned URLs for chunked upload, and a webhook fires when a new report is generated.
Install Jentic One Beta
Connect the Paraspot API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Paraspot 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%2Fparaspot.ai%2Fparaspot" | 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%2Fparaspot.ai%2Fparaspot" | 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 Paraspot API.
Register and update property units and generate inspection scan links
Create and update tenancies tied to a property unit
Retrieve inspection reports and their past scans for a unit
Update a report's inspection type and the resident data attached to it
Upload scan videos and request presigned URLs for chunked media upload
Track scan status and receive a webhook when a new report is generated
Use Cases
Patterns agents use Paraspot API for, with concrete tasks.
★ AI Agent Inspection Workflow
An AI agent coordinating move-in and move-out inspections can create a unit, issue a scan link, and pull the resulting report through Jentic. The agent searches for each operation, supplies the unit and tenancy details, and advances the workflow, without the developer wiring the bearer token or reading the Paraspot reference docs.
Call POST /units/generate_scan_link to issue a scan link for a unit, then GET /reports/get_all to list its reports
Report Retrieval and Review
Property managers review the AI-generated condition reports produced from tenant scans. The report operations return a report's main details, list the past scans behind it, and let a manager set the inspection type, so a dashboard can show the latest inspection and its history for each unit.
Call GET /reports/get to read a report's details, then GET /reports/get_past_scans for its scan history
Portfolio and Tenancy Setup
Onboarding a new building means registering its properties and units and attaching tenancies. Paraspot lists and creates properties, creates units beneath them, and records tenancies, so an agent can stand up a portfolio before the first inspection is scheduled.
Call POST /properties/create to add a property, then POST /units/new to add a unit to it
Key Endpoints
22 endpoints — the paraspot api manages rental property units, tenancies, and the ai-generated inspection reports produced from tenant video scans.
METHOD
PATH
DESCRIPTION
GET
/units/list
List units
POST
/units/new
Create a new unit
POST
/units/generate_scan_link
Generate a scan link for a unit
GET
/reports/get_all
List all reports for a unit
GET
/reports/get
Get report main details
GET
/reports/get_past_scans
List past scans for a report
POST
/tenancies/create
Create a tenancy
GET
/properties/list
List properties
GET
/units/list
List units
POST
/units/new
Create a new unit
POST
/units/generate_scan_link
Generate a scan link for a unit
GET
/reports/get_all
List all reports for a unit
GET
/reports/get
Get report main details
GET
/reports/get_past_scans
List past scans for a report
POST
/tenancies/create
Create a tenancy
GET
/properties/list
List properties
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.
P
Paraspot API
- Foundational (C-)53/100
64
Foundational Compliance82
Developer Experience & Jentic Compatibility28
AI-Readiness & Agent Experience94
Agent Usability60
Security62
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
64
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
96%
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).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
82
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
55%
Example Density
How richly the API is illustrated with examples.
99%
Example Validity
Percentage of examples that conform to their schemas.
74%
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.
28
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
62%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
62
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
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 Paraspot API by hand means sending its bearer token, generating scan links, and uploading inspection videos through presigned URLs yourself. Through Jentic you install once, import Paraspot from the API Directory, store the token once, and your agent calls it.
Permission scoping
You choose the exact Paraspot operations a rule allows, such as listing units and retrieving reports, so write operations like removing a unit or a property stay out of reach. The agent can read and advance inspections within that set and nothing beyond it.
Credential isolation
Your Paraspot bearer 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.
Intent-based discovery
Agents search Jentic by intent such as 'generate an inspection scan link' or 'get an inspection report', and Jentic returns the matching Paraspot 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 Paraspot API through Jentic.
What authentication does the Paraspot API use?
The Paraspot API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context.
Can I retrieve inspection reports with the Paraspot API?
Yes. The report operations return a report's main details and the past scans behind it, and you can list every report tied to a unit. The inspection type and resident data on a report can be updated through their own operations.
What are the rate limits for the Paraspot API?
The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://www.paraspot.ai for the limits that apply to your account tier.
How do I run an inspection workflow with the Paraspot API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Paraspot from the API Directory, and store your bearer token once. Your agent then searches for an intent such as 'generate an inspection scan link', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Paraspot MCP server?
You do not need an MCP server to give your agent the Paraspot API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the unit, report, and media operations on demand, which keeps your agent's context free of an extra server's tool definitions.
Can I limit what my agent is allowed to do with the Paraspot API?
Yes. Paraspot has write operations like creating and removing units and properties, so you can allow your agent only the ones a task needs, such as listing units and reading reports, while leaving out removing a unit or a property. Because you run Jentic One yourself, the agent reads inspection data but cannot delete records unless you add those operations, and every call is logged.
GET STARTED