PlanACCOUNT
PreviewConnect a production key to load account truth.Developer control plane · Australia
Everything around the AU API. Nothing pretending to be the product.
Manage production access, inspect live account usage, run explicit Australia-scoped requests, understand jurisdiction coverage, connect AI clients and handle billing from one customer workspace.
Requests this windowUSAGE
—Authenticated usage only.RemainingLIMIT
—Reset not loaded.API healthEDGE
CheckingPublic operational health; not property-level coverage.Production credential
Connected account
No production key connectedPreview mode only
DISCONNECTEDCountry scope
FIXEDAustralia routes are pre-scoped to country=AU in Request Lab.
Credential handling
CONTROLLEDSession-only by default. Persistent storage only if the customer explicitly chooses it.
Execution state
Preview vs Production
Preview
ACTIVEExplore workspace structure and public coverage without account telemetry or live property calls.
Production
LOCKEDRequires a validated PropData key and an explicit Production mode selection before Request Lab can execute.
No sandbox fiction: Production mode calls the real PropData API. The workspace never simulates customer usage, entitlements or property responses.
This browser session
Recent requests
| Time | Route | Status | Latency | Mode |
|---|---|---|---|---|
| No production requests in this session. | ||||
Australia Request Lab
Run explicit production requests.
The lab is account-gated and Production-only. Australia property routes automatically include country=AU; the connected key is sent only in the x-api-key header.
⌁
Connect a production key to use Request Lab
The public workspace does not execute property requests. Connect and validate an existing PropData key, then switch to Production.
Account usage
Live allowance and endpoint activity.
Usage is loaded from the authenticated account response. Missing fields remain unavailable rather than being inferred from public pricing.
▥
Usage is account-gated
Connect a validated production key to load the actual plan, used requests, remaining allowance, reset metadata and endpoint breakdown supplied by the API.
PlanLIVE
—Reported or mapped by the authenticated account response.UsedWINDOW
—Requests reported in the active usage window.RemainingWINDOW
—Calculated only when a limit is reported.Total reportedLIFETIME
—Cumulative only when supplied by the API.Allowance
Authenticated account
Waiting for usage data—
Endpoint activity
API keys
Production credential inventory.
Key management is exposed only when the connected account and production API advertise it. Secrets are never reconstructed or invented.
⌁
API keys are account-gated
Connect a production key first. If this account supports key inventory, the workspace will load it from /v1/auth/keys.
| Name | Key | Created | Last used | Status | Action |
|---|
Australia coverage
National identity. Jurisdiction-native depth.
A successful national property identity does not imply every cadastral or geometry layer is available. Match, coverage and provenance remain separate application signals.
16,970,406 geocoded address records across all 9 source partitions. GDA2020 baseline.
BASELINE COMPLETE2,156,480 certified lot parcels with state-native identity and promoted polygon geometry.
LIVE4,303,714 parcel records with PFI/UFI source semantics retained.
LIVE439,539 cadastral parcels preserving PID, volume, folio and UFI context.
LIVE152,986 legal blocks with block, section, division, district and lifecycle semantics.
LIVEReplacement statewide build remains pinned-source-revision gated before production promotion.
NEXTNational G-NAF identity live. Deeper cadastre remains authoritative-delivery / rights gated.
CADASTRE GATEDNational identity live. Deeper jurisdiction layers remain source / commercial-use gated.
CADASTRE GATEDCoverage rule: unknown stays unknown. PropData does not infer an equivalent cadastral fact from another jurisdiction when the authoritative Australia layer has not been promoted.
MCP + AI
OAuth-protected AI access.
REST key connection and MCP authorization are different security flows. Never paste a static PropData API key into a chat or MCP client authorization field.
Connector endpoint
PropData MCP
Use the OAuth-protected connector with compatible clients. Australia workflows can carry the same country scope through the supported tool contract.
https://propdata-mcp.sales-fd3.workers.dev/mcpOAuth authorization
REQUIREDClient authorization is handled by the MCP flow, not your REST key.
Security boundary
REST ≠ MCP
REST
API KEYProduction requests use x-api-key from trusted application infrastructure.
MCP
OAUTHCompatible AI clients use the OAuth-protected connector flow.
Billing
Plan and subscription controls.
Connected account details come from live usage where available. Public AU pricing remains the source for current self-serve package offers.
Connect a production key to load the account tier and allowance reported by PropData.
Need a different contract?
Enterprise delivery
Bulk, state extracts, OAuth MCP, white-label infrastructure, custom response contracts and multi-country PropData are handled through enterprise agreements.
Contact sales