- If you connected through the browser sign-in, the allowance belongs to you.
- If you’re using a team API key, the allowance belongs to your team.
How rows are counted
Calls that fail don’t use any rows.
Searches return up to 50 rows per page by default and at most 200 per page. Your assistant can ask for further pages if it needs them.
Checking your usage
Every tool result includes aquota section with four values:
You can also ask your assistant “How much of my REalyse allowance have I used?” It will call
get_current_user (not available with team API keys).
When you’ve used 80% of your allowance, results start to include a notice. At 95% the notice becomes a warning.
When you reach the limit
- If a search would return more rows than you have left, you get a shorter final page that uses up what remains.
- Trend and statistics tools need every requested series to fit in your remaining allowance. If they don’t fit, the call is refused rather than returning partial figures.
- Once you have no rows left, data tools return a message telling you when the allowance resets. Lookup tools such as
resolve_locationkeep working.
Other limits
A few tools have extra limits to protect shared services:- Title plan maps:
get_title_plan_mapis limited to a set number of maps per user per hour. - Landmark lookups: when
resolve_locationorresolve_radius_locationhas to geocode a landmark rather than a postcode or known place, those lookups are limited per user per hour. - Land ownership:
get_land_ownershiphandles one title at a time. If it’s busy, your assistant should wait and try again. Results marked as partial or truncated are incomplete. - Parallel calls: your assistant can run up to three REalyse tool calls at the same time.