The ASINT API
Three surfaces: property valuation, vehicle valuation and the location index. One format, one authentication scheme, one data model underneath them.
What is available
The valuation model documentation is published and open — you can read it before we agree on anything.
Link Home
Valuation of apartments and houses. Inputs: district, mahalla, area, floor, room count, building type, finish condition.
Link Home documentation →Link Auto
Vehicle valuation. Inputs: make, model, year, mileage, body type, transmission, fuel, condition, region.
Link Auto documentation →GeoScore
The location index for a coordinate: a score for each of the nine subindexes on an absolute 0–100 scale. A batch mode exists for processing addresses in bulk.
GeoScore methodology →Organisation console
For bank and company teams: roles (super admin, admin, API manager, auditor, employee), inviting staff, organisation API keys, the audit log and security — step by step.
Organisation guide →Get your own key — 3 requests free
Anyone can sign in, create a key and start calling the API. No contract, no call with sales.
3 free requests
Every account gets 3 full requests on us, across both apartments and cars. Failed requests are never charged.
15,000 UZS per request
After the free ones, each request is charged to your balance — the same price for apartments and cars. Top up with Click whenever you like; there is no subscription.
One request is everything
The valuation with its price range and drivers, the district or model forecast, and the finished report — advanced (full multi-page) or simple (one page), as PDF or HTML.
A dashboard for it all
Sign in to create and revoke keys, see your balance and free requests left, top up, and watch your usage day by day and request by request.
Sign in or register, then open Settings → Developers.
Request format
REST over JSON. The response always carries more than a number — an interval and a confidence level, because a valuation without them cannot be defended to a credit committee.
Three lines to get started: create a key, POST the property, read the result. Field lists and error codes are in the per-model documentation above.
POST /service/v1/home
X-API-Key: dk_xxxxxxxx_...
Content-Type: application/json
{
"district": "Yunusobod",
"area": 62,
"rooms": 3,
"floor": 4,
"total_floors": 9,
"renovation": "evro",
"report_type": "advanced", // or "simple"
"format": "pdf", // or "html"
"lang": "en" // en | ru | uz
}
-> 200
{
"request": { "free": true, "charged": 0, "free_left": 2 },
"valuation": { "predicted_price": 78400, "price_range": [72100, 85200], ... },
"forecast": { "series": { "change_pct": 3.1, ... } },
"report": { "format": "pdf", "encoding": "base64", "content": "JVBERi0x..." }
}Access and limits
Keys are issued against a use case: we look first at the volume and the segments you need.
Authentication
An API key in the X-API-Key header. Create one yourself in your account, or have your organisation issue them.
Format
REST, JSON in and JSON out. A Swagger description is available on request.
Batch processing
One request returns the valuation, the market forecast and the finished report together. Bulk processing for organisations is available on request.
Limits
Personal keys: 3 free requests, then pay as you go. Organisations: limits set by contract.
For organisations: your own team, one balance, your own keys
Banks, insurers, agencies and developers can open an organisation account. A super admin creates and manages the team; everyone works under one shared balance, with a full audit trail.
Staff accounts
The super admin adds colleagues by email. Each person gets a single-use activation link and picks their own password — nobody emails passwords.
Shared balance
Evaluations by every employee draw on the organisation’s balance, topped up centrally, instead of each person funding their own.
Organisation API keys
Keys for your own systems — hashed, optionally expiring, revocable, with last use and request counts. They act on behalf of the employee who issued them.
Audit trail and access control
An append-only activity log with CSV export, an IP allowlist, two-factor sign-in and dual control for role changes.
An MCP server for AI agents
Alongside REST we expose an MCP server, so assistants and agents built on large language models can query valuation and location data directly, without a separate integration written for each tool.
The practical difference: an agent does not need someone to write a wrapper for it. It receives a description of the available tools and calls them itself. If you are building an internal assistant for a bank or an agency, this is the shortest path.
Request MCP accessHow it usually gets connected
The three scenarios people arrive with most often.
Pre-screening applications
Automated valuation at the front of the mortgage pipeline: some applications are filtered out or confirmed without sending an appraiser.
Collateral portfolio monitoring
Periodic revaluation of the whole portfolio in a batch request, instead of a manual quarterly re-appraisal.
Location risk in scoring
Risk subindexes as an input to the credit decision: a threshold on natural or technogenic hazard changes the insurance requirement or the LTV.
Need a key, or a pilot?
Describe the use case and the expected volume — we will propose a plan and give you test access