Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
คำอธิบายจากผู้ทำ (ภาษาอังกฤษตามต้นฉบับ)
Quantum-sealed audit logs for AI agents (ML-DSA-87, SHA3-512), plus Privi Guard and trust passports.
สามเรื่องนี้ไม่รวมเป็นคะแนนเดียว เพราะความเห็น การวัด และความนิยม เป็นคนละเรื่องกัน
ตัวนี้ยังไม่ได้เรียบเรียงเป็นภาษาไทย ด้านล่างคือข้อเท็จจริงที่เราอ่านจาก registry
เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง
ต้องเตรียมก่อน
คุณใช้แอปไหน
เลือกแอปด้านบน เราจำไว้ให้ ครั้งหน้าปุ่มจะขึ้นว่า “ติดตั้งลง …”
ใช้ได้ทั้ง Claude บนเว็บ แอปคอมพิวเตอร์ และมือถือ:
https://privi-ledger.onrender.com/mcpพิมพ์คำสั่งนี้ใน Terminal
claude mcp add --transport http privi-ledger https://privi-ledger.onrender.com/mcpวางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"privi-ledger": {
"url": "https://privi-ledger.onrender.com/mcp"
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"privi-ledger": {
"type": "http",
"url": "https://privi-ledger.onrender.com/mcp"
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
ChatGPT ต่อได้เฉพาะ server ที่อยู่บนอินเทอร์เน็ต:
https://privi-ledger.onrender.com/mcpชื่อเมนูอาจต่างกันเล็กน้อยตามแพ็กเกจและรุ่นของแอป
ตัวเลือกเก็บในคุกกี้บนเครื่องนี้ ไม่ต้องมีบัญชี
ค่าตั้งนี้สร้างจากข้อมูลใน registry ของผู้ทำ ถ้าไม่ตรงกับ README ให้เชื่อ README
ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 7 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน
privi_token_marketPRIVI on Base: price, how much PRIVI and USDC the Privi swap desk holds (so whether a swap can fill), any Uniswap v3 / Aerodrome pools, and optionally a swap quote. Every paid Privi tool also accepts PRIVI. Free.
ledger_pricingList Privi Ledger tools, what each costs, and how to get an organization key.
ledger_check_receiptConfirm that an action receipt exists in the ledger and when it was recorded. Reveals no action contents. Free.
ledger_audit_streamCheck whether an agent's action log is intact: entry count, time span, action and failure counts, head hash, and where tampering broke the chain if it did. Does not reveal the actions themselves. Paid per call via x402.
ledger_record_actionAppend an action to the organization's tamper-evident log. Returns the entry with its entry_hash receipt. Requires the organization API key.
ledger_read_streamRead your organization's entries in a stream, oldest first, with an integrity check of the whole stream. Requires the organization API key.
ledger_list_streamsList your organization's streams with entry counts. Requires the organization API key.
ledger_compliance_reportAudit-ready report of your AI agents' activity for a period (SOC 2 evidence, security questionnaires, AI-regulation record keeping): actions by type, failures, human approvals, log integrity, on-chain status, and findings. The report's hash is anchored on the Privi blockchain so
ledger_report_pdfA finished PDF of a sealed compliance report, for auditors and customers. Returned as base64 (pdf_base64) and as an embedded PDF resource; also downloadable at /reports/ .pdf with the organization key. Requires the organization API key.
ledger_verify_reportCheck that a compliance report is unaltered: recomputes its hash, confirms Privi Ledger issued it, and checks the anchor on chain (Base, until the Privi chain mainnet). Free; no key needed.
ledger_signupCreate a Privi Ledger organization on the free plan and get its API key (shown once; store it). Free plan: up to the monthly entry limit, all tools included. Upgrade any time with ledger_upgrade_pro. No key needed to sign up.
ledger_planYour plan, entries used this month, the limit, and when a Pro plan renews. Requires your organization API key.
ledger_upgrade_proBuy 30 days of Privi Ledger Pro (unlimited entries) for your organization, paid in USDC on Base via x402. Each call adds 30 days. Requires your organization API key.
gov_ai_usecase_saveAdd or update an entry in your agency's AI use case inventory (OMB M-25-21). Every change creates a new version and is written to your tamper-evident 'ai-inventory' log. Requires the organization API key.
gov_ai_inventoryYour agency's AI use case inventory: the current version of each record. Requires the organization API key.
gov_ai_inventory_checkFlags what an OMB M-25-21 review would flag before you submit: missing required fields, PII without a Privacy Impact Assessment, and high-impact AI in pilot or deployment missing any minimum risk practice (testing, impact assessment, independent review, monitoring, operator train
gov_ai_inventory_exportMachine-readable CSV of your publicly releasable AI use cases (for publishing at agency.gov/ai), with its SHA-256 sealed on chain (Base, until the Privi chain mainnet) so the published file can be proven unaltered. Requires the organization API key.
gov_ai_verify_exportCheck that a published AI inventory file is exactly what the agency exported from Privi Ledger, and return its on-chain seal. Free; no key needed.
gov_pqc_classifyClassify cryptographic algorithms as quantum-vulnerable (RSA, ECDH, ECDSA, EdDSA, DH, DSA, MQV), post-quantum (ML-KEM, ML-DSA, SLH-DSA), hybrid, symmetric/hash, or unknown. Free.
gov_pqc_system_saveRecord the cryptographic inventory (CBOM) of one system for post-quantum migration. Every change creates a new version and is written to the agency's tamper-evident 'pqc-inventory' log. Scanners and agents can submit results directly. Requires the organization API key.
gov_pqc_inventoryCurrent cryptographic inventory of your systems. Requires the organization API key.
gov_pqc_planPrioritized post-quantum migration plan: every quantum-vulnerable asset ranked (High Value Assets, high-impact systems and long-lived sensitive data first; key establishment before signatures), with its deadline (key establishment Dec 31 2030, signatures Dec 31 2031), recommended
gov_pqc_exportExport the full cryptographic inventory (CBOM) and migration plan as one JSON document for OMB, the CIO or auditors, with its SHA-256 sealed on chain (Base, until the Privi chain mainnet). Requires the organization API key.
gov_pqc_verify_exportCheck that a CBOM and migration-plan document is exactly what was exported from Privi Ledger and return its on-chain seal. Free; no key needed.
ledger_handshake_offerStart a Privi Handshake: a two-sided record of a dealing with another company's agent (payment, data transfer, delivery, agreement). Recorded in your log now; when the other company accepts, both logs hold matching entries and the pair is sealed on chain (Base). Requires your org
ledger_handshake_inboxHandshakes sent to and from your organization, newest first, with their terms and status. Requires your organization API key.
ledger_handshake_acceptAccept a handshake addressed to your organization: records the same terms in your log, confirms it in the other company's log, and seals the matched pair on chain (Base). Requires your organization API key. Read the terms first with ledger_handshake_inbox.
ledger_handshake_rejectReject a handshake addressed to your organization; the other company's log records the rejection. Requires your organization API key.
ledger_handshake_verifyPublic check of a handshake: both companies, status, whether both matching log entries still exist, and the on-chain seal. Never reveals the terms. Free; useful for disputes and audits.
passport_issueIssue a Privi Passport: a signed, on-chain-anchored trust credential for your agent or organization, scored 0-1000 (grade A-E) from verified history, integrity, anchoring, reliability, human oversight, compliance reports and confirmed handshakes. Show it to counterparties; they v
passport_verifyCheck an AI agent's Privi Passport before trusting it: Privi signature, content unaltered, not expired or revoked, anchor on chain (Base), and a live re-score of the agent right now (so tampering after issue is caught). Free; no key needed.
passport_gateOne-call allow/deny decision before transacting with another AI agent: verifies its Privi Passport and applies your minimums, returning the reasons. If you send your organization API key the decision is recorded in your own tamper-evident log as due-diligence evidence. Free.
passport_listYour organization's issued passports with score, grade, expiry and revocation. Requires the organization API key.
passport_revokeRevoke one of your passports (e.g. an agent was retired or compromised). Verifiers see it immediately. Requires the organization API key.
kya_checkKnow-Your-Agent for blockchains: is this wallet operated by an audited AI agent, and how trustworthy is it right now? Resolves the address to its organization and live Privi Passport and returns allow/deny with reasons, plus a Privi-signed attestation (valid 60 min) you can cache
kya_challengeStep 1 of binding a wallet to your Privi Passport: get a message to sign with that wallet (EIP-191 personal_sign). Valid 30 minutes. Requires the organization API key.
kya_bind_walletStep 2: bind the wallet to your organization's Privi Passport so its transactions pass KYA checks. With a wallet signature the binding is *proven*; without one it is only *declared* (most checkers require proven). Requires the organization API key.
kya_walletsWallets bound to your organization and how each was proven. Requires the organization API key.
kya_unbind_walletRemove a wallet from your Passport (rotated or compromised key). KYA checks deny it immediately. Requires the organization API key.
mandate_createDraft a Privi Mandate: the human's signed permission for your agent to spend, with a budget, per-payment cap, allowed payees and expiry. Returns sign_url: send it to the human, who reads the plain-English terms and signs once with their wallet (free, no transaction). Nothing can
mandate_checkFor merchants, payment facilitators and counterparties: did a human authorize this AI agent to pay you this amount? Verifies the human's wallet signature, status, expiry, per-payment cap, remaining budget and payee list, and returns allow/deny with reasons plus a Privi-signed att
mandate_spendCall before each payment: checks the mandate and, if allowed, deducts the amount from the budget and records the payment in the agent's tamper-evident log. Refused payments are logged as blocked. Refused at once if the kill switch is on. Over the organization's live-approval thre
mandate_getPublic view of a mandate: terms, status, the human's signature, spent and remaining budget, and recent spends. Free.
mandate_listYour organization's mandates with status and remaining budget. Requires the organization API key.
mandate_revokeStop an agent from spending under a mandate (the human can also revoke from the sign_url page). Requires the organization API key.
fortress_keysPrivi's public signing keys: Ed25519 and ML-DSA-87 (NIST FIPS 204, CNSA 2.0 post-quantum). Pin these to verify Privi signatures offline. Free.
ledger_tree_headThe latest signed tree head of Privi's transparency log: an RFC 9162 Merkle root over every entry ever recorded, signed with Ed25519 and ML-DSA-87, and periodically anchored on chain (Base). Free.
ledger_inclusion_proofMerkle audit path proving an entry is in Privi's append-only transparency log (RFC 9162). Verifiable offline against the signed tree head. Reveals no entry contents. Free.
ledger_consistency_proofProof that Privi's log only grew between two signed tree heads: nothing recorded earlier was edited, removed or reordered (RFC 9162). Free.
fortress_tpi_policyDefine a Two-Person Integrity policy: which officers can approve, and how many distinct approvals an action needs. Requires the organization API key.
fortress_tpi_requestAsk officers to authorize a sensitive action under a two-person policy. Returns approve_url for the officers; each signs with their wallet. Do not act until fortress_tpi_status shows 'authorized', then call fortress_tpi_execute. Requires the organization API key.
fortress_tpi_statusStatus of a two-person request (pending, authorized, vetoed, expired, executed) and who approved. Free.
fortress_tpi_executeConsume a two-person authorization right before performing the action. Single use; refused unless authorized. Requires the organization API key.
qledger_statusPrivi Quantum Ledger: latest quantum-sealed block (SHA3-512, ML-DSA-87 + Ed25519), entries waiting for the next block, the Privi Foundation chain it is fused with, and signing keys. Free.
qledger_blockOne quantum-sealed block with its signatures, settlement on chain and a validity check. Free.
qledger_verify_chainVerify the whole Quantum Ledger: SHA3-512 block hashes, hash links, both signatures on every block, and for recent blocks the log roots, entry roots and RFC 9162 consistency proofs. Free; anyone can run it.
qledger_entry_proofProve an entry (by its receipt hash) is sealed in a quantum block: the block, its post-quantum signatures, its on-chain settlement and the Merkle inclusion proof. Reveals no entry contents. Free.
qledger_sealSeal your newest entries into a quantum block now instead of waiting for the next scheduled block (every few minutes). Does nothing if no entries are waiting. Requires the organization API key.
fortress_tpi_listYour organization's two-person requests. Requires the organization API key.
ledger_evidence_bundleExport a self-contained evidence package for auditors, courts or air-gapped systems: every entry, the hash chain, an RFC 9162 inclusion proof, the signed tree head, on-chain checkpoint and Privi's keys, signed with Ed25519 and ML-DSA-87. Verify offline with verify_bundle.py (GET
เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 8 พ.ย. 2569
ชื่อใน registry ยืนยันด้วยบัญชี GitHub canoydario847-cloud ซึ่งเป็นเจ้าของ repo
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ตอบกลับใน 264 ms (HTTP 200)
ไม่ต้องล็อกอิน
อ่านคำอธิบายเครื่องมือ 60 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI
เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo
จากการตรวจเบื้องต้นของเรา ผ่าน 3 จาก 3 ข้อที่ตรวจได้ เรายังไม่ได้อ่านโค้ด ก่อนใส่กุญแจหรือ token ให้ดูว่า server ขอสิทธิ์อะไร และเลือกกุญแจที่ทำได้เท่าที่จำเป็น
registry ไม่ได้ระบุว่าต้องใช้กุญแจ แต่บางตัวจะขอให้ล็อกอินตอนใช้ครั้งแรก
รันบนคลาวด์ของผู้ทำ ต่อผ่านอินเทอร์เน็ตได้เลย ไม่ต้องลงโปรแกรม แต่ข้อมูลที่ส่งให้จะผ่านเซิร์ฟเวอร์ของผู้ทำ
repo บน GitHub มีการแก้โค้ดล่าสุด – และส่งรุ่นล่าสุด (0.12.1) เข้า registry 12 วันที่ผ่านมา
โปรแกรมที่รองรับ MCP เช่น Claude Desktop, Claude Code, Cursor และ VS Code ตัวนี้ต่อผ่าน URL จึงใช้กับโปรแกรมที่รับ remote MCP ได้ เช่น ChatGPT ที่เปิดโหมดนักพัฒนา
ในหมวดเดียวกันมี Finance Toolkit, SolidInvoice, Korea Tax Calculator
server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว
อ่านการ์ด:↓ ดาวน์โหลดต่อสัปดาห์i★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
ส่วนนี้คัดจาก repo ของผู้ทำตามต้นฉบับ PopNx MCP ไม่ได้ตรวจหรือรับรองเนื้อหา ตัด HTML รูปภาพ และสคริปต์ออกแล้ว ลิงก์จะพาออกนอกเว็บ
*(formerly Privi Ledger)*
Quantum-sealed, tamper-evident audit logs for AI agents. Every company running agents needs to prove what those agents did: what data they touched, what they paid for, what they changed, and that nobody rewrote the record afterwards. Privi Ledger gives any MCP-capable agent a place to log each action, and gives auditors a way to verify the log, paid per check in USDC on Base via x402.
Works with Claude, ChatGPT, Cursor, VS Code and custom agents. Built by Privi World Co on the same record technology as Privi Verify.
Live (testnet): https://privi-ledger.onrender.com/mcp
Real-time tools (live_*, approval_*, trust_events, gateway_*, room_*) are described under *Privi Live* below.
| Tool | Access | What it does |
|---|---|---|
ledger_pricing | free | Prices, network, action types, how to get a key |
ledger_check_receipt | free | Confirms an action receipt (entry_hash) exists and when; reveals no contents |
ledger_audit_stream | $0.02 (x402) | Integrity audit of an agent's log: intact or not, where it broke, counts, time span, head hash. No action contents |
ledger_record_action | org key | Append an action; returns the entry and its entry_hash receipt |
ledger_read_stream | org key | Read your own entries with an integrity check |
ledger_list_streams | org key | Your streams and entry counts |
ledger_compliance_report | org key | Audit-ready report of agent activity for a period, sealed on the Privi chain |
ledger_report_pdf | org key | The sealed report as a finished PDF (also at GET /reports/ .pdf with the org key) |
ledger_handshake_offer / _accept / _reject / _inbox | org key | Privi Handshake: two-sided records of dealings between companies |
ledger_handshake_verify | free | Public check of a handshake and its on-chain seal; never reveals terms |
ledger_verify_report | free | Proves a report is unaltered and was issued by Privi Ledger; checks its on-chain seal |
Action types: tool_call, data_access, data_change, payment, message, decision, approval, error, other. Outcomes: success, failure, pending, blocked.
Each entry's SHA-256 fingerprint covers its contents and the previous entry's fingerprint in the same stream. Editing, deleting or reordering any entry breaks the chain from that point, and audits report the exact entry where it broke. Organizations only ever see their own streams; API keys are stored as hashes.
Stream heads are anchored on the Privi blockchain every few minutes (see On-chain checkpoints), so integrity can be proven without trusting Privi.
| Plan | How | Includes |
|---|---|---|
| Free | ledger_signup (no key needed) | Every tool, up to 500 entries per month |
| Pro | ledger_upgrade_pro, $29 USDC per 30 days via x402 | Unlimited entries; each payment adds 30 days |
| Enterprise | Created by Privi (/admin/orgs) | Unlimited; billed by agreement |
Any company, or an AI agent acting for one, can sign up, start logging, and upgrade without talking to anyone. Payments go straight to LEDGER_PAY_TO, and each purchase is recorded in the organization's own privi-billing stream. ledger_plan shows usage and renewal. Set LEDGER_FREE_MONTHLY and LEDGER_PRICE_PRO_MONTH to change the limits.
Create an organization with the admin key (set LEDGER_ADMIN_KEY):
curl -X POST https://<host>/admin/orgs \
-H "Authorization: Bearer $LEDGER_ADMIN_KEY" -H 'Content-Type: application/json' \ -d '{"name": "Acme Robotics"}'
The customer adds the server to their agent with header Authorization: Bearer plk_..., and tells it to call ledger_record_action after each meaningful action. They share their org_id and stream names with auditors, who call ledger_audit_stream.
ledger_compliance_report turns an organization's agent logs into evidence for SOC 2 reviews, customer security questionnaires and AI-regulation record keeping. For any period it reports actions by type, actors, failures, blocked actions, human approvals, log integrity and on-chain status. It also lists findings an auditor would raise, such as broken integrity, logs not yet anchored, failed actions, or payments and data changes with no human approval recorded. The result comes as JSON plus a ready-to-share Markdown version.
Each report is sealed. Its SHA-256 hash, taken over canonical JSON, is anchored on the Privi blockchain through Privi Anchor. Anyone holding the report can run ledger_verify_report, which recomputes the hash, confirms Privi Ledger issued exactly that content, and checks the anchor on chain. Editing even one number, such as hiding a failure, makes verification fail.
Federal agencies must keep an inventory of their AI use cases, publish the releasable ones as a machine-readable file, and show minimum risk practices for high-impact AI. That requirement comes from OMB Memorandum M-25-21 and OMB's guidance on 2025 agency AI reporting. Privi Ledger covers the whole loop:
| Tool | What it does |
|---|---|
gov_ai_usecase_save | Add or update a use case in the guidance's reporting fields. Every change is a new version, written to the agency's tamper-evident ai-inventory log |
gov_ai_inventory | Current inventory |
gov_ai_inventory_check | Flags what a review would flag: missing required fields, PII without a Privacy Impact Assessment, and high-impact AI in pilot or deployment missing any minimum practice (testing, impact assessment, independent review, monitoring, operator training, fail-safe, appeals, public feedback) or without a recently active activity log as monitoring evidence. Practices waived by a written CAIO determination are respected |
gov_ai_inventory_export | CSV of releasable use cases for agency.gov/ai, with its SHA-256 sealed on the Privi chain |
gov_ai_verify_export (free) | Proves a published inventory file is exactly what the agency exported |
The inventory links to agents' Privi Ledger activity logs (monitoring_streams), so "ongoing monitoring" is backed by real, tamper-evident records.
Field names follow OMB's published reporting fields. Confirm them against OMB's current template before submitting. This tool supports compliance work; it is not legal advice or an OMB-approved system.
Executive Order 14409 (June 2026) requires federal key establishment to move to post-quantum cryptography by Dec 31, 2030, and digital signatures by Dec 31, 2031. OMB M-26-15 asks every agency for a migration plan built on a cryptographic inventory (CBOM), prioritizing High Value Assets, high-impact systems and data that must stay sensitive past 2030, plus TLS 1.3 support by Jan 2, 2030.
| Tool | What it does |
|---|---|
gov_pqc_classify (free) | Classifies algorithms and cipher suites: quantum-vulnerable (RSA, ECDH, ECDSA, EdDSA, DH, DSA, MQV), post-quantum (ML-KEM, ML-DSA, SLH-DSA), hybrid, symmetric/hash, or unknown |
gov_pqc_system_save | Records one system's cryptographic assets (from people, scanners or agents). Versioned and written to a tamper-evident pqc-inventory log |
gov_pqc_inventory | Current inventory |
gov_pqc_plan | Ranked migration queue with per-asset deadlines and NIST replacements, progress metrics, and findings: targets past the deadline, TLS below 1.3, priority assets with no target date, unrecognized algorithms |
gov_pqc_export | The CBOM plus plan as one JSON document, sealed on the Privi chain |
gov_pqc_verify_export (free) | Proves an exported document is unaltered |
The rules follow public summaries of EO 14409 and OMB M-26-15. Confirm them against the official texts and NIST IR 8547 before relying on them. This tool supports compliance work; it is not legal advice.
The feature no one else can copy: a signed, on-chain-anchored credential that says how much an AI agent can be trusted, scored 0-1000 from evidence only Privi Ledger holds.
| Component | Max | Evidence |
|---|---|---|
| history | 300 | verified entries and days of activity |
| integrity | 250 | every hash chain still verifies (all or nothing) |
| anchoring | 150 | share of streams whose on-chain checkpoint matches the record |
| reliability | 100 | 1 - failure rate |
| oversight | 50 | human approvals on sensitive actions |
| compliance | 100 | a sealed compliance report exists and is clean |
| handshakes | 50 | deals other Privi organizations confirmed |
Grades: A >= 850, B >= 700, C >= 550, D >= 400, E below. Valid 30 days.
passport_issue (org key; free on Pro/enterprise, $LEDGER_PRICE_PASSPORT via x402 on the free plan) - Ed25519-signed by the server, hash anchored on the Privi chain, every component itemised.passport_verify (free) - signature, content, expiry, revocation, chain anchor, and a live re-score: if the agent's history is tampered with after issue, the passport fails.passport_gate (free) - one-call allow/deny with your minimums (min_score, min_grade, require_anchored); send your own key and the decision is written to your log as due-diligence evidence.passport_list, passport_revoke (org key).GET /passports/ (JSON + live verification), GET /passports/ /badge.svg (embeddable badge), GET /.well-known/privi-passport.json (issuer public key).Why it compounds: agents that gate on passports push their counterparties onto Privi Ledger; every logged action, report and handshake raises the score; a better score wins more deals. Set LEDGER_PASSPORT_SIGNING_KEY (32-byte hex Ed25519 seed) to pin the issuer key across redeploys; otherwise one is generated and stored in the database.
As AI agents become the main senders of on-chain transactions, every chain, DeFi protocol, exchange, stablecoin issuer and x402 facilitator needs one answer before accepting a transaction: is this wallet operated by an audited agent, and how trustworthy is it right now? Privi KYA answers it, and only Privi can, because the answer is the Passport.
kya_challenge + kya_bind_wallet (org key) - bind a wallet to your Passport by signing a Privi challenge with the wallet (EIP-191 personal_sign, recovered in pure Python; no web3 dependency). A binding without a signature is only *declared*.kya_check (free) - resolves the wallet to its organization and live Passport; returns allow/deny with reasons, the current score and grade, and a Privi-signed KYA attestation valid 60 minutes that a facilitator can cache and verify offline. Send your key and the decision is logged as evidence.kya_wallets, kya_unbind_wallet (org key) - rotated or compromised keys are denied immediately.GET /kya/connect — paste the org key, connect MetaMask, sign once; done. No code needed.GET /kya/ (JSON verdict + attestation; ?min_score=&min_grade=&require_signed=), GET /kya/ /badge.svg.Integration pattern for a chain or protocol: before accepting an agent transaction, GET /kya/ ; require allow: true (and optionally proof: "signature"); keep the attestation + signature as your compliance record.
The whole log is sealed into a chain of quantum blocks every few minutes (LEDGER_QBLOCK_INTERVAL, default 300 s):
ตัดมาแค่ช่วงต้น อ่านต่อใน repo