Skip to content

Personal service: connect, verify, save and export

Use an ordinary personal account. The examples have isolated acceptance evidence and selected production delivery evidence; they do not show that every production scenario passed. The static website never accepts passwords, tokens, private records or deletion credentials. See tested clients. The account, each connected app's access, exports and deletion are managed in the Argus web app.

The service is a free public beta with no billing in this phase (ADR 0008). This does not promise permanent free access, unlimited use or all-market coverage. Prices are end-of-day only; Argus offers no real-time or intraday data. Source dates, gaps, rights and resource limits remain part of every result. Accounts are for individuals aged 18 or over, for non-professional use; mainland China and sanctioned regions are excluded. No institutional employer, department or enterprise administrator is needed for personal registration. Client registration and personal signup are separate; only registered OAuth clients and callbacks work. Do not paste credentials into a chat or a request file.

Authorize only the data you need

Run argus auth login, review the live argus tool-registry, and use the trusted account application to grant private domain access to your registered client. A signed fact scope does not grant a private read or write. Private operations need both signed scopes and active owner consent. Subscription creation additionally needs personal:subscriptions:background; export needs personal:export and the intersection of requested readable domains. Reconnect if the signed scopes change. Account revocation, deletion and sensitive identity changes require recent owner verification and confirmation in the trusted account flow; an Agent cannot approve them with a boolean flag.

The composed detail/comparison/filing tools also require an explicit signed tool grant from the registered issuer: argus:tools:personal-facts or an explicit signed tool allowlist. Both paths still require facts:read and evidence:read. The default everyday fact whitelist does not automatically include them. Until your client has that verified grant, use the existing underlying fact tools or the trusted personal fact pages. Discovery and a copied example do not create a grant.

Execute the same example through your chosen interface

The downloadable request templates are the parameterized inputs exercised by the isolated acceptance test. Replace every $variable with a value obtained from your authorized environment, retain JSON types, and write only the selected request object to a private UTF-8 file. Generate a new write key for a new intended mutation; preserve it with identical input on retry. Each $write_key belongs to its own operation; do not reuse one key throughout the sequence. A placeholder such as $company or $filing_question represents a whole typed object, not a string containing serialized JSON.

For example, the company-facts template becomes a request file after resolving one company and an aware as_of. Execute it with argus personal-company-detail-read-v1 --request-file company.json. REST uses the live OpenAPI path for personal_company_detail_read_v1, a registered API session or supported OAuth Bearer from secure runtime storage, and the same JSON object. The public OAuth MCP endpoint does not serve the personal tools: tools/list there shows up to 20 consumer tools, depending on the connection's grants, and the personal tools are neither listed nor callable. Personal results use personal-result-v1: check transport status/isError, then problem, payload, audit_id, owner lifecycle and the per-tool result schema. Original financial tools retain their existing envelope. Do not add owner, institution or trusted session claims to the JSON. See transport contracts.

The example sequence

Template Inputs and checks
company-facts Supply a resolved company subject and query time. Read every child package's facts, evidence, quality, license and actual calls; partial data is not complete coverage.
two-etfs Supply two distinct resolved ETF subjects and a time covered by both. The sample compares disclosed holding counts, not return forecasts or a quality rating. Preserve reporting-date and basis conflicts; a missing field remains missing.
filing-evidence Supply an exact company, source concept, accounting basis, periods, query time and filing accessions. Follow each selected fact to evidence; your Agent organizes the answer. Distinguish disclosed reasons from arithmetic and general definitions.
watch-save, watch-member Save an empty owner list, then use its returned object ID and a security selected from the master-data resolver. Ambiguous tickers require an exchange or explicit selection. A watchlist alone does not start background work.
research-save Save your own annotation with origin: user_text. It is private user content, never an Argus investment judgment or permission to copy restricted source text.
subscription After explicit background consent, choose earnings, material filing and dividend events for the selected security. The 300-second check interval is not a promise of immediate source availability. Delivery is to the private inbox and authorized Agent reads; it does not send email or webhooks.
usage Read the actual last 24 hours. Statistics lag/completeness, success, denial and failure classes remain visible; current rate windows are separate from historic successes.
export, export-status, export-download Request the readable research domain, retain the returned export ID, poll actual status, then issue a short reference after the worker finishes. Send the reference only in the authenticated POST body to /v1/personal/export-content, or use argus personal-export-content --request-file download.json --output export.zip. Never create a public download URL.

Request and result examples

Tool-page examples also include saved queries and confirmation preparation. Saved queries use the selected tool's normalized Registry parameters; for company_fact_snapshot, use company_id rather than ticker. Confirmation preparation validates the nested target request separately from its outer request. The tool-page list-deletion preparation example also requires a list with affected subscriptions and the current deletion-impact version. A list without such dependencies uses ordinary authorized deletion and needs no confirmation. The numeric filing example supplies accounting basis, an exact period and a filing accession. Missing selectors return clarification_required with zero business calls, rather than a disclosed numeric answer.

An independently usable usage request file contains only this JSON object:

{"request_id":"example-usage","hours":24}
argus auth login
argus personal-usage-read-v1 --request-file usage.json

This requires personal:usage:read and current owner consent. For REST, use the current OpenAPI binding and the API-resource credential. All personal results require the per-tool result check; a legacy success test would reject a valid personal response or overlook its coded problem:

def personal_payload(response):
    # First handle HTTP failure, or MCP JSON-RPC failure / isError.
    if response["problem"] is not None:
        raise RuntimeError({"problem": response["problem"],
                            "audit_id": response["audit_id"]})
    if response["payload"] is None:
        raise RuntimeError("Missing personal payload")
    return response["payload"]

For the company template, $company must contain kind: "company", the resolved subject_id, the matching resolved security_id and a nonempty resolved ticker. None of these identity fields may be guessed from a company name. Use the exact identifiers returned by your authorized resolver and an aware as_of within captured coverage. An ETF subject uses kind: "etf" and the same returned security ID for both subject_id and security_id. Inspect DetailSubject and FilingQuestion in the tool schema before substituting those objects; a LEI, ticker, CIK and security ID are different identifier types.

After a completed export-download call, copy only payload.data.reference into a private download.json body as reference; offset is an optional integer byte offset, defaulting to zero. The content endpoint accepts neither request_id nor the export ID in place of that reference. Keep the credential from the same API/MCP resource, client and session that issued the reference. For CLI downloads, use a reference issued by the CLI's API session and a new output path. The content response is ZIP bytes, not a personal JSON envelope. A truncated transfer is incomplete even if its headers succeeded.

Full personal export requires the trusted owner flow after recent verification. It is separate from source financial-data export. Download retries still check current access, expiry and source rights. Revocation/deletion blocks new delivery; already downloaded files cannot be recalled. Edits use returned object versions; bulk actions or overwrites require a server-bound owner approval. Handle denied, conflicting and expired requests explicitly rather than retrying them unchanged.

Reproducible evidence and limits

Isolated ordinary-account checks replay the existing hash-verified SEC captures: Apple and Microsoft disclosures and distinct SPY and MDY holdings. SPY has 504 disclosed holdings and MDY 400 in those captured source versions; these are not claims about today's funds. Source timestamps and immutable evidence remain unchanged. Source transport is replayed in isolation while identity, database, Redis, actual HTTP CLI/REST and the Python MCP client execute real paths. The transport harness uses an explicitly signed disposable grant for composed tools; this is distinct from the real Casdoor owner login and consent checks, and does not assert that the production issuer is already configured for them. The security selector catalog used for mutation tests is an explicitly labelled disposable fixture, not production security-master coverage.

The supported-client matrix distinguishes this companion MCP path from hosted connectors; of those, only Claude has been tested end to end, and it uses the consumer tools rather than these examples. Restricted or unknown source rights produce a coded refusal; a reference alone never grants display, storage, notification, export or external-model processing rights. A lawful financial research intent does not itself block authorized facts; the official workflow never produces a recommendation, target price, predicted return or trade instruction.