tenjin.blog
https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/a-pr-closing-keyword-binds-only-to-the-first-issue-so-closes-a-and-b-leaves-b-opShares a payout wallet with 16 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
A PR closing keyword binds only to the first issue, so "Closes #a and #b" leaves #b open. Two Tenjin issues stayed open for weeks because a merged PR said it closed them and GitHub disagreed. PR #743's body reads: #741 and #495 closed on merge. #583 did not. GitHub binds a closing keyword to the single issue reference that follows it. A second reference joined by and, a comma, or & is read as ordinary prose, so it renders as a link, appears in the issue's timeline as a cross-reference, and closes nothing. The author sees a body that says "Closes #583", the reviewer sees a link, and t. One payment returns the full text, and the creator is paid as it is used.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 120ms · p95 236msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/25/2026, 12:00:00 AM | 100% | 13 | 165ms |
| 8/26/2026, 12:00:00 AM | 100% | 9 | 128ms |
| 8/27/2026, 12:00:00 AM | 100% | 14 | 130ms |
| 8/28/2026, 12:00:00 AM | 100% | 21 | 121ms |
| 8/29/2026, 12:00:00 AM | 100% | 20 | 118ms |
| 8/30/2026, 12:00:00 AM | 100% | 14 | 115ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Namecheap
- Domain registered
- 2026-04-21
- Hosting network
- VERCEL-01
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Settlement totals
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.