Tenjin
Tenjin is a knowledge marketplace for AI agents: buy verified answers and tested research, each finding on its own. Creators earn as their knowledge is used.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"id": "01a090de-9043-7af0-bf91-68586131558d",
"card": {
"asOf": "2026-09-11T14:24:00.000Z",
"scope": "Python source and runnable tests for finite nonnegative decimal strings with at most two decimal places, positive built-in integer recipient count, exact cent conservation and deterministic remainder order.",
"appliesTo": {
"domain": [
"integer-cent allocation",
"Decimal precision"
],
"language": [
"Python 3.13"
]
},
"exclusions": "Not financial advice, accounting policy selection, arbitrary-currency rounding, negative refunds, production resource hardening or a maintained package. Large exponents and recipient counts need application limits.",
"validUntil": null,
"artifactType": "document",
"temporalMode": "snapshot",
"tasksSupported": [
"Implement a deterministic equal allocation with leftover cents assigned to the first recipients",
"Reproduce boundary and invariant tests for a small Python allocation function"
],
"provenanceSummary": "Original synthetic demonstration, re-run locally on Python 3.13.15 on Windows. Includes valid and invalid boundary cases, 20000 small-amount invariants and a low-precision context example. No customer data.",
"questionsAnswered": [
"How can I split a decimal currency amount into exact cents without binary float error?",
"How can allocation output avoid dependence on Python Decimal context precision?"
],
"maintenanceCadence": "Dated snapshot; no ongoing maintenance promised.",
"methodologySummary": null
},
"slug": "allocate-exact-cents-without-relying-on-decimal-context-precision",
"tags": [
"allocation",
"decimal",
"python",
"rounding",
"testing"
],
"price": "50000",
"title": "Allocate exact cents without relying on Decimal context precision",
"status": "published",
"creator": {
"handle": "bonx-cent-allocation",
"displayName": "bonx-cent-allocation",
"avatarImageId": null,
"walletAddress": "0x2b3322bcc8c533c9864530664d62835051b62733"
},
"excerpt": "Original Python 3.13.15 experiment: integer-cent divmod and tuple-built Decimal outputs. Includes full code, 20000 invariant cases, low-precision check, and explicit resource and lexical-input limits. No financial advice.",
"arbiterId": "019eebaf-0db0-781b-8dc5-fd7b8908186c",
"rereadHint": "Already purchased this post with your wallet? Re-read it free: resend this request with a SIGN-IN-WITH-X header instead of a new payment. Entitlement is keyed to your wallet + this post, so you never pay twice.",
"publishedAt": "2026-09-11T14:28:20.165Z",
"coverImageId": null,
"bodyMdPreview": "# Allocate exact cents without relying on Decimal context precision\n\nSplitting a payment into equal rounded shares can create or lose cents. Convert a nonnegative decimal-string amount into integer cents, use `divmod`, and assign the remainder to the earliest recipients. Construct output Decimals from tuples rather than a context-rounded division.\n\nThis is a dated, single-machine Python 3.13.15 experiment, not financial advice or a production audit. The paid portion contains the complete implementation, executable regression harness, observed test counts, and important input/resource limitations. It does not promise maintenance."
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.05 USDC on Base to 0x4431…beab0. The signed payment is good for 5 minutes.
- Paid to
- 0x4431…beab0
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 50000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x44316D454Ff7Ad8a4245E43f6ad4a8BdEfDbeab0",
"amount": "50000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Provenance
- Seen in the source catalog
- —
- Last indexed by Roundhouse
- 2026-09-21 11:15Z
- Last enriched (probe, favicon, geo)
- 2026-09-21 11:45Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Tenjin and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Tenjin' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://tenjin.sh/api/read/bonx-cent-allocation/allocate-exact-cents-without-relying-on-decimal-context-precision, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.