Agent Tooling

The complete API surface this platform exposes to AI agents and client applications — and how agents discover and drive the site.

API Catalog

29 endpoints across 6 categories. Every route this platform exposes to agents and clients.

29 tools

Agent Endpoints

3
POST/app/api/agentMulti-turn conversation with tool calling — the primary interface for AI agents interacting with this platform.
GET/app/api/v1/agent/query-listingsSearch active listings by price, beds, and neighborhood.
neighborhoodmax_pricemin_beds
POST/app/api/v1/agent/calculate-carryMonthly carrying cost including mortgage, HOA, and NYC taxes.
* purchase_pricedown_payment_pctinterest_rate_pct

Listings & Content

5
GET/app/api/listingsAll active listings with gallery images.
GET/app/api/blogBlog index — published articles and guides.
GET/app/api/blog/[slug]A single blog post by slug.
GET/app/api/v1/testimonialsClient testimonials from the Webflow CMS.
GET/app/api/v1/agentsTeam members from the Webflow CMS.

Neighborhoods

5
GET/app/api/neighborhoodsMarket stats for a neighborhood from NYC DOF rolling sales.
* neighborhood
GET/app/api/neighborhood-statsNeighborhood building stock from PLUTO (land-use data).
GET/app/api/v1/neighborhoodIndex of neighborhoods with public data.
GET/app/api/v1/neighborhood/[name]Transit, schools, and street trees for one neighborhood.
GET/app/api/v1/neighborhoods/cmsNeighborhood guides from the Webflow CMS.

NYC Public Data

8
GET/app/api/nyc/buildingEight municipal datasets in a single call — zoning, tax, violations, and more.
* bbl
GET/app/api/plutoLot and zoning data for an address.
* address
GET/app/api/acrisRecorded sales and deeds.
* bbl
GET/app/api/assessmentsDOF property valuation and assessment roll.
* address
GET/app/api/transitNearby subway stations with distance and status.
* lat* lon
GET/app/api/treesNearby street trees with species and health data.
* lat* lon
GET/app/api/wikiWikipedia summary for a neighborhood.
* neighborhood
GET/app/api/geocodeAddress to coordinates.
* address

Calculators

4
GET/app/api/calculators/mortgageMortgage payment estimation — POST to calculate.
GET/app/api/calculators/affordabilityHome affordability estimation — POST to calculate.
GET/app/api/calculators/closing-costsClosing cost estimation — POST to calculate.
GET/app/api/calculators/rentalRental yield and carry analysis — POST to calculate.

Forms & Messaging

4
POST/app/api/contactSubmit an inquiry to the team.
POST/app/api/formsStore a form response.
GET/app/api/forms/schema/[formId]JSON schema for a form.
POST/app/api/sync-rentalsSync rentals from the upstream feed.

Agent Discovery & WebMCP

How automated agents find, understand, and operate this site — the machine-readable surfaces (well-known files, llms.txt, OpenAPI) and the WebMCP tool layer that lets an in-browser agent drive the site directly.

What /.well-known/ is

/.well-known/ is a reserved path prefix defined by RFC 8615. Applications register a name (for example security.txt or change-password) and publish site-wide metadata at a predictable location so a client can discover it before interacting with the origin.

Two rules matter here:

  1. Well-known URIs are rooted at the domain root. /.well-known/example is well-known; /app/.well-known/example is not. The prefix only counts at the top of the path.
  2. A missing file is allowed. Clients must not assume one exists.

This site's Cloud app is mounted at /app, while the domain root is the Webflow marketing site. So the app serves its copies at /app/.well-known/… — reachable and useful, but technically app-relative metadata, not an RFC 8615 well-known URI. Publishing the true root-level files is a Webflow-site task.

Discovery surfaces

PathWhat it isServed by
/app/.well-known/webmcpWebMCP tool catalogue (static mirror of the live registry)Cloud app
/app/.well-known/webmcp.jsonSame catalogue at the filename the WebMCP registry convention expectsCloud app
/app/.well-known/agent-manifest.jsonProvider manifest — endpoints, tools, data attributionCloud app
/app/.well-known/agent-card.jsonTool definitions with parameters and endpointsCloud app
/app/.well-known/agents.txtIntent tiers, rate limits, human-gated submission policyCloud app
/app/llms.txtShort machine-readable site summaryCloud app
/app/llms-full.txtComplete corpus (listings, guides, team)Cloud app
/app/openapi.yamlOpenAPI 3.1 spec for the REST endpointsCloud app
/app/robots.txtCrawl rules (the authoritative file is at the domain root)Cloud app

Every app response also carries a Link header advertising these surfaces, so a client that only issues a HEAD request can find them without parsing HTML:

Link: </app/.well-known/webmcp>; rel="webmcp", </app/.well-known/agent-card.json>; rel="service-desc", …

WebMCP

WebMCP is an emerging W3C Web Machine Learning Community Group proposal. It lets a page register structured tools — named functions with JSON Schema inputs — that an AI agent running in the same browser can call directly. The agent calls execute(); the tool runs on the page with the user watching. It mirrors the Model Context Protocol tool shape, but the transport is the JavaScript heap instead of HTTP.

Runtime surfaces

  • Imperative API — document.modelContext.registerTool({ name, title, description, inputSchema, annotations, execute }).
  • Declarative API — annotate an ordinary <form> with toolname, tooldescription, toolautosubmit, and per-field toolparamdescription. The browser synthesises the schema from the controls, and SubmitEvent.agentInvoked tells the submit handler an agent (rather than a human) triggered it.
  • Live registry — public/shared/webmcp-tools.js, loaded on every page.
  • Static manifest — src/lib/webmcp-manifest.ts, served at /app/.well-known/webmcp. Keep it in sync with the live registry when tools change.

Discovery wiring

  • <link rel="webmcp" href="/app/.well-known/webmcp" /> in the document head.
  • Link: …; rel="webmcp" on every response (see next.config.ts).

Annotations

Tools declare intent so an agent can decide when to confirm or sanitise:

AnnotationMeaning
readOnlyHintNo state change; confirmation may be skipped.
consequentialHintSignificant / non-reversible — the agent or browser can force user confirmation.
untrustedContentHintOutput contains user-generated or third-party content; apply heightened scrutiny.

Human in the loop

Form tools are readable and fillable by any agent, but submission is designed to keep a human present. When an agent activates an intake tool, the page switches to that form so the visitor can watch it happen; a missing required answer is returned to the model as a message to ask the user for it, never invented.

Verify

# The catalogue
curl -s https://www.jamesfinelliteam.com/app/.well-known/webmcp | head

# Discovery link header on any response
curl -sI https://www.jamesfinelliteam.com/app | grep -i '^link:'

# Registered tools in the page console (Chrome 149+, WebMCP enabled)
await document.modelContext.getTools()

Related

  • Access policy and rate tiers: /app/.well-known/agents.txt
  • Provider manifest: /app/.well-known/agent-manifest.json
  • Developer documentation: /app/docs