Immobiliareimmobiliare.it

ScoredJul 30, 2026, 07:48 AM

Immobiliare's API design is a genuine strength — the contract is machine-readable and well-shaped, giving partners a solid foundation to build on. However, the program has two critical gaps that will stall partner adoption: agents and developers cannot discover, understand, or reliably execute against your APIs without manual intervention, and there is no self-serve path to a first working call.

API DesignA clean, typed, well-governed API contract agents can reason about3 pass2 warn0 fail90A+
SignalPointsFindingsRationale
passSchema coverage & depthvia sdk25/25package.json "types" → dist/index.d.ts. Investigated: sdk 100%, spec 50%.Typed, complete request/response schemas are what make agent function-calling possible.
passAuth declared & discoverablevia spec25/25Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.Agents can only authenticate when auth is declared, scoped, and discoverable.
warnMachine-readable, versioned contractvia spec18.8/25info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
passSecurity & governance hygienevia spec15/15No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
warnExample coveragevia sdk5/10README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, docs 0%.Examples carry shape semantics schemas under-specify — for humans and agents alike.
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples2 pass0 warn3 fail55D
SignalPointsFindingsRationale
passQuickstart presentvia docs25/25Quickstart at https://insights.immobiliare.it/webdocs/getting-started with a runnable first-call sample. Investigated: docs 100%.A quickstart is the fastest path from landing page to first successful call.
passDescription completenessvia spec15/1592% of operations + parameters have substantive descriptions. Investigated: spec 100%.Complete descriptions are the context humans and agents need to use endpoints.
failSelf-service developer portalvia docs0/29No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.Self-serve key/account creation is the fast first call for partners, with no sales gate.
failCode samples in docsvia docs0/18No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.Multi-language samples shorten time-to-first-call.
failChangelog publishedvia spec0/13No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.A published changelog lets partners track changes without surprise.
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass2 warn1 fail62C
SignalPointsFindingsRationale
passRegistry & SDK presencevia docs28/28Indexed on Context7 (immobiliare/fastify-sentry, 20 snippets). Investigated: docs 100%, sdk 58%, cli 0%.Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
warnDocs reachable, not hard auth-gatedvia docs15/301 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
warnCrawlable / AEOvia wellknown9/12Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
failllms.txt present, valid & comprehensivevia docs0/30No llms.txt found at any candidate location (https://insights.immobiliare.it/webdocs/llms.txt, https://insights.immobiliare.it/llms.txt, https://insights.immobiliare.it/docs/llms.txt). Investigated: docs 0%, sdk 0%.A valid, comprehensive llms.txt is the machine-readable entry point for agents.
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs1 pass1 warn3 fail61C
SignalPointsFindingsRationale
passMachine-readable errors (RFC 9457)via spec28/28error codes documented in the docs site at https://insights.immobiliare.it/webdocs/errors. Investigated: spec 100%, docs 100%.RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
warnAgent-navigable, token-efficient docsvia docs18.9/22No pages support .md URLs (0/1 tested). Investigated: docs 86%.Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
failOperation purpose clarityvia spec0/250% of operations are agent-inferable. Investigated: spec 0%.Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
failAgent instructions file (AGENTS.md)via wellknown0/10No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
failDocs structured datavia docs0/8Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
naDescription consistency across surfaces—/7Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.Every surface tells the same story about what the product is.
Agent UsabilityAgents have the context to use your APIs reliably, not just find them0 pass1 warn3 fail43F
SignalPointsFindingsRationale
warnSandbox separationvia sdk10/20No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.An isolated environment lets agents exercise destructive operations safely.
failIdempotency documentedvia spec0/270% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.Documented idempotency lets agents retry safely.
failRate-limit signalingvia spec0/22No rate-limit response headers documented. Investigated: spec 0%, docs 0%.Machine-readable rate-limit headers let agents throttle adaptively.
failRunnable collection with test scriptsvia platform0/9No public Postman workspace discovered for the org. Investigated: platform 0%.A public, maintained collection with assertions is runnable truth agents validate against.
naPagination documented & consistent—/22No surface produced evidence for this capability in this run.Consistent, documented pagination lets agents traverse collections.
Resources Discovered

The public resources we found for Immobiliare — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hintsContext7 (20)
APIs analyzed1Immobiliare.it - Listing Integration
Want to improve your results?