Install Jentic One Beta

Connect the Microburbs Property Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microburbs Property Data 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.

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%2Fmicroburbs.com.au%2Fmicroburbs" | sh

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%2Fmicroburbs.com.au%2Fmicroburbs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Microburbs Property Data API.

Resolve an Australian street address to a GNAF property ID with the geocode address operation

Get a property's automated valuation with predicted_price and its low and high range

Read a property's sale history, rent history, and comparable recent sales nearby

Check property hazards including bushfire, flood, historical flood, landslide, erosion, and heritage

GET STARTED

Start building with Microburbs Property Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Microburbs Property Data API for, with concrete tasks.

★ Property research agent through Jentic

A buyer's agent or property research assistant answers questions about a specific Australian address. Through Jentic it resolves the address to a gnaf_id, then calls the AVM, sale history, and risks operations for that property and summarises value, past sales, and hazards. Your Microburbs key stays on your own Jentic One instance, and your rules can hold the agent to the property operations you choose so it does not run up per-call costs elsewhere.

GET /v1/geocode/address with address '27 Arlington St, Belmont North NSW', then GET /v1/properties/GANSW704074813/valuation/avm and /v1/properties/GANSW704074813/risks/all and summarise the result

Suburb screening for investors

Investors comparing markets can screen every Australian suburb with the finder search, filtering by states and property_type and sorting by fields such as grossYield, vacancyRate, or growthForecast4yr. The count operation sizes the result first, and each shortlisted suburb can be followed up with its market, forecast, and supply-pressure operations.

GET /v1/suburbs/finder/search with states 'QLD', property_type 'house', sort '-grossYield', limit 20, then GET /v1/suburbs/{suburb_name}/market/vacancy-rate for each result

Hazard and risk checks for lending and insurance

Lenders and insurers can check a property's exposure before quoting. The risks operations cover bushfire, flood, historical flood, landslide, erosion, high-voltage power lines, mobile black spots, and environment, and the risks/all bundle returns them in one call at a flat bundle price.

GET /v1/properties/GAVIC419929404/risks/all and flag any non-empty bushfire or flood result

Suburb profiles for listings and content

Real estate portals and agencies can add suburb context to a listing: median price and rent series, demographics such as age and income, school catchments, crime summaries, lifestyle points of interest, and boundary shapes as GeoJSON for maps.

GET /v1/suburbs/Unley/profile, /v1/suburbs/Unley/market/median-sale-price-series, and /v1/suburbs/Unley/shapes/boundary with geojson true

Key Endpoints

174 endpoints — the microburbs property data api returns suburb and property data for australian localities, keyed to gnaf property ids and abs suburb names.

METHOD

PATH

DESCRIPTION

GET

/v1/geocode/address

Resolve an address to a GNAF ID

GET

/v1/properties/{gnaf_id}/valuation/avm

Automated valuation

GET

/v1/properties/{gnaf_id}/sale-history

Property sale history

GET

/v1/properties/{gnaf_id}/risks/all

All property risks

GET

/v1/suburbs/{suburb_name}/profile

Suburb profile

GET

/v1/suburbs/{suburb_name}/market/all

All suburb market indicators

GET

/v1/suburbs/finder/search

Search and rank suburbs

GET

/v1/geocode/address

Resolve an address to a GNAF ID

GET

/v1/properties/{gnaf_id}/valuation/avm

Automated valuation

GET

/v1/properties/{gnaf_id}/sale-history

Property sale history

GET

/v1/properties/{gnaf_id}/risks/all

All property risks

GET

/v1/suburbs/{suburb_name}/profile

Suburb profile

GET

/v1/suburbs/{suburb_name}/market/all

All suburb market indicators

GET

/v1/suburbs/finder/search

Search and rank suburbs

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Microburbs by hand means handling its bearer key, resolving addresses to GNAF IDs first, branching on null data responses, and reading per-call cost headers. Through Jentic you install once, import Microburbs from the API Directory, store the key once, and your agent calls it.

Permission scoping

Microburbs puts the property gnaf_id and the suburb_name in the URL path (/v1/properties/{gnaf_id}/...), so a rule can limit your agent to one property or suburb and the operations you pick. Because every call is metered, choosing a narrow operation set also bounds what the agent can spend.

Credential isolation

Your Microburbs 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 'flood risk for an Australian address' or 'median rent in a suburb', and Jentic returns the matching Microburbs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Microburbs Property Data API through Jentic.

What authentication does the Microburbs Property Data API use?

Per its OpenAPI spec, the Microburbs API uses an API key sent as a bearer token (BearerAuth): `Authorization: Bearer <key>`. The key `test` works as a public sandbox for a fixed set of sample properties and suburbs at no cost, and any other value needs a key minted on the Microburbs developer portal. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when the agent calls.

How is the Microburbs API priced?

Pricing is per endpoint and prepaid. Every metered response carries X-Cost-Cents with the exact cents billed, X-Spent-Cents and X-Remaining-Cents for the wallet, and calls stop when the remaining credit reaches zero. Bundle endpoints such as /v1/properties/{gnaf_id}/risks/all ship at a flat bundle price.

How do I value a property through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Microburbs API from the directory, and store your key. Your agent searches 'get an automated valuation for an Australian property', resolves the address with GET /v1/geocode/address, then calls GET /v1/properties/{gnaf_id}/valuation/avm. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Microburbs API?

Yes. For example, allow only GET /v1/geocode/address and the /v1/properties/{gnaf_id}/valuation and risks operations, so a lending assistant can value and risk-check addresses but cannot run up per-call charges on the suburb demographic and lifestyle endpoints. Every call it makes is logged.

Is there a Microburbs MCP server?

Yes - Microburbs offers an official MCP server, documented in its API reference. You can also connect the Microburbs API directly through Jentic: your agent gets the full 174-endpoint surface from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

What are the rate limits for the Microburbs API?

The OpenAPI spec does not state numeric rate limits; it documents 429 responses for throttling. Check the Microburbs API docs at https://www.microburbs.com.au/developers/api-docs for current limits.

What happens when Microburbs has no data for a property?

The call still returns HTTP 200, with data set to null, available false, and a stable reason slug such as no_avm_for_GANSW704074813 plus a human-readable message. Branch on data being non-null rather than on the status code.

Microburbs Property Data API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentAddress Validationbearer174 EndpointsREST

For Agents

Look up Australian property and suburb data: resolve an address to a GNAF ID, then get valuations, sales and rent history, risks, demographics, and market indicators.

Use for: What is 27 Arlington St, Belmont North worth?, Check whether this property is in a bushfire or flood zone, Get the median rent and rental yield for Subiaco, Find all suburbs in Queensland with high gross yield and low vacancy

Not supported: Does not cover properties outside Australia, list properties for sale on your behalf, or process mortgage applications. Use for Australian property and suburb data lookups only.

The Microburbs Property Data API returns suburb and property data for Australian localities, keyed to GNAF property IDs and ABS suburb names. It resolves an address to a gnaf_id, then returns a property's automated valuation (AVM), sale and rent history, comparables, zoning, nearby schools and transport, and risk layers such as bushfire, flood, landslide, and heritage. At suburb level it covers median sale price and rent series, yield, days on market, sale forecasts, demographics, crime, schools, development applications, and boundary shapes, plus a suburb finder that filters and sorts across the country. Pricing is per endpoint, and every metered response reports its cost in the X-Cost-Cents header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

92%

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).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

10%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

49%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: CSignals: 1

55%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Microburbs Property Data API to your agent

Capabilities

Start building with Microburbs Property Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Microburbs Property Data API

Jentic AI Readiness Score

Microburbs Property Data API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness