Qmlm Work Jiadi Property API
43
AI ReadinessFoundational (D)43/100
Community OpenAPI document · agent-readyFinanceAccountingbearer23 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Record account balances and asset transactions in Jiadi, take net worth snapshots, compare them over time, and read net worth history.
Use for: What is my current net worth in Jiadi?, Update my savings account balance to 12,500, Take a snapshot of my balances for this month, Compare this month's snapshot with last month's
Not supported: Does not connect to banks, execute trades, or file taxes. Use for manually tracked asset balances, records, and net worth snapshots in Jiadi only.
The Jiadi Property API tracks a person's assets and net worth: it records accounts with a type, category, and currency, updates each account's balance in a workspace that totals net worth, and logs asset records with an amount, description, and occurredAt date. It captures point-in-time snapshots of all balances, compares two snapshots to show what changed, and returns a net worth history for charting. It is the backend for the Jiadi personal asset management app.
Install Jentic One Beta
Connect the Jiadi Property API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jiadi Property 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.
1
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%2Fqmlm.work%2Fqmlm" | sh2
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%2Fqmlm.work%2Fqmlm" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Jiadi Property API.
Create asset accounts with a name, type, category, and currency, and update or retire them
Update an account's balance in the workspace and read the workspace net worth
Log asset records with amount, description, and occurredAt, and list them between start and end dates
Take a snapshot of all balances with a note and amend the latest one
Compare two snapshots with the from and to parameters to see what changed
Read the net worth history series for charting
Set the user's mainCurrency and monthlySnapshotDay preferences
Use Cases
Patterns agents use Jiadi Property API for, with concrete tasks.
★ Agent-maintained net worth tracker through Jentic
A personal finance agent keeps Jiadi current: after the user reports new balances, it updates each account in the workspace and takes a snapshot. Through Jentic the JWT is injected by the developer's own Jentic One instance, and a rule can keep the agent away from account deletion and password changes.
POST /api/workspace/balance/{id} with balance 12500 for the savings account, then POST /api/snapshots with note 'November close'
Month-over-month change report
Seeing how wealth moved is the point of snapshots. GET /api/snapshots lists the history, and GET /api/snapshots/diff takes a required from snapshot and an optional to snapshot to return the difference, which an agent can turn into a plain-language summary of gains and losses.
GET /api/snapshots, pick the two most recent ids, call GET /api/snapshots/diff with from and to, and summarise the change per account
Asset transaction logging
Individual movements such as dividends, purchases, or transfers are stored as asset records. POST /api/records requires amount, description, and occurredAt, and GET /api/records filters by start and end so the agent can review a period.
POST /api/records with amount 300, description 'ETF dividend', occurredAt '2026-11-11', then GET /api/records with start '2026-11-01'
Net worth charting
For dashboards, GET /api/reports/net-worth-history returns the series used to chart net worth over time, and GET /api/workspace gives the current balances and total, so an agent can answer trend questions or feed a chart.
GET /api/reports/net-worth-history and GET /api/workspace, then report the current net worth and its trend
Key Endpoints
23 endpoints — the jiadi property api tracks a person's assets and net worth: it records accounts with a type, category, and currency, updates each account's balance in a workspace that totals net worth, and logs asset records with an amount, description, and occurredat date.
METHOD
PATH
DESCRIPTION
GET
/api/workspace
Get balances and net worth
POST
/api/workspace/balance/{id}
Update an account balance
POST
/api/snapshots
Create a snapshot
GET
/api/snapshots/diff
Compare two snapshots
POST
/api/records
Create an asset record
GET
/api/records
List asset records
GET
/api/reports/net-worth-history
Net worth history
POST
/api/accounts
Create an account
GET
/api/workspace
Get balances and net worth
POST
/api/workspace/balance/{id}
Update an account balance
POST
/api/snapshots
Create a snapshot
GET
/api/snapshots/diff
Compare two snapshots
POST
/api/records
Create an asset record
GET
/api/records
List asset records
GET
/api/reports/net-worth-history
Net worth history
POST
/api/accounts
Create an account
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
J
Jiadi Property API
- Foundational (D)43/100
99
Foundational Compliance57
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability75
Security60
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
29%
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.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
15%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
59%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
60
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
60%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Jiadi by hand means logging in with a username and password to get a JWT, then attaching that bearer token to every account, snapshot, and record call yourself. Through Jentic you install once, import the Jiadi Property API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Jiadi puts account, snapshot, and record ids in the URL path (/api/workspace/balance/{id}, /api/records/{id}), so a rule can limit your agent to one account's balance. You choose the operations it may call, so destructive ones like account deletion or snapshot deletion are not included unless you add them.
Credential isolation
Your Jiadi JWT 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 'take a net worth snapshot' or 'compare two snapshots', and Jentic returns the matching Jiadi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Jiadi Property API through Jentic.
What authentication does the Jiadi Property API use?
The Jiadi Property API declares an HTTP bearer scheme (BearerAuth) with a JWT format in its OpenAPI spec. You obtain the token from POST /api/login with a username and password; register, login, and the ping health check need no credential. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time.
Can I compare two net worth snapshots with the Jiadi Property API?
Yes. GET /api/snapshots/diff takes a required from snapshot and an optional to snapshot and returns the difference between them. Use GET /api/snapshots to find the snapshot ids, and GET /api/snapshots/{id} for one snapshot's account balances.
What are the rate limits for the Jiadi Property API?
The OpenAPI spec does not specify rate limits, and no public documentation for limits is linked from it. Treat the API as a personal app backend and keep agent polling light.
How do I update an account balance in Jiadi through Jentic?
Install Jentic One, import the Jiadi Property API from the Jentic API Directory, and store your JWT. Your agent searches for 'update an account balance', Jentic returns POST /api/workspace/balance/{id} with its schema, and the agent calls it with the account id and the new balance. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Jiadi Property MCP server?
You don't need an MCP server to give your agent the Jiadi Property API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.
Can I limit what my agent is allowed to do with the Jiadi Property API?
Yes. Write a rule that allows GET /api/workspace, GET /api/snapshots, GET /api/snapshots/diff, and GET /api/reports/net-worth-history, so the agent can report net worth and changes but cannot edit balances, delete snapshots, or change your password. Every call it makes is logged.
GET STARTED