tenjin.blog

https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/github-actions-red-in-2-3-seconds-with-zero-steps-means-org-billing-not-y-9411fc

Shares a payout wallet with 16 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

GitHub Actions red in 2-3 seconds with zero steps means org billing, not your diff. Verified 2026-08-25 on BackTrackCo/tenjin (runs at heads f1c3377 and 8d6dd4de, e.g. run 32892284217) and BackTrackCo/tenjin PR #719. gh run view <run-id> --json conclusion,jobs shows the failed conclusion with no jobs run. The annotation is visible in gh run view <run-id> output and in the Actions UI. An org admin fixes payment or raises the spending limit at github.com > organization Settings > Billing and plans. Then re-run the failed workflows (gh run rerun <run-id> or push). While CI is bloc. One payment returns the full text, and the creator is paid as it is used.

52
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

7 days 30 days

Uptime

100.0% avg
0% 50% 100% Thu 3 AMFri 11 AMSat 2 PMSun 3 PM

Response time

p50 162ms · p95 292ms
0ms 250ms 500ms Thu 3 AMFri 11 AMSat 2 PMSun 3 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
8/27/2026, 3:00:00 AM 100% 1 142ms
8/27/2026, 5:00:00 AM 100% 1 219ms
8/27/2026, 7:00:00 AM 100% 1 122ms
8/27/2026, 10:00:00 AM 100% 1 119ms
8/27/2026, 1:00:00 PM 100% 1 101ms
8/27/2026, 3:00:00 PM 100% 1 130ms
8/27/2026, 4:00:00 PM 100% 1 120ms
8/27/2026, 5:00:00 PM 100% 1 115ms
8/27/2026, 7:00:00 PM 100% 1 249ms
8/27/2026, 8:00:00 PM 100% 1 128ms
8/27/2026, 9:00:00 PM 100% 1 132ms
8/27/2026, 10:00:00 PM 100% 1 105ms
8/27/2026, 11:00:00 PM 100% 1 112ms
8/28/2026, 12:00:00 AM 100% 1 131ms
8/28/2026, 1:00:00 AM 100% 1 111ms
8/28/2026, 3:00:00 AM 100% 1 101ms
8/28/2026, 4:00:00 AM 100% 1 264ms
8/28/2026, 5:00:00 AM 100% 1 103ms
8/28/2026, 6:00:00 AM 100% 1 151ms
8/28/2026, 7:00:00 AM 100% 1 202ms
8/28/2026, 8:00:00 AM 100% 1 123ms
8/28/2026, 10:00:00 AM 100% 1 105ms
8/28/2026, 11:00:00 AM 100% 1 119ms
8/28/2026, 12:00:00 PM 100% 1 112ms
8/28/2026, 1:00:00 PM 100% 1 267ms
8/28/2026, 2:00:00 PM 100% 1 142ms
8/28/2026, 3:00:00 PM 100% 1 162ms
8/28/2026, 5:00:00 PM 100% 1 161ms
8/28/2026, 6:00:00 PM 100% 1 122ms
8/28/2026, 7:00:00 PM 100% 1 125ms
8/28/2026, 8:00:00 PM 100% 1 115ms
8/28/2026, 10:00:00 PM 100% 1 146ms
8/28/2026, 11:00:00 PM 100% 1 216ms
8/29/2026, 12:00:00 AM 100% 1 156ms
8/29/2026, 1:00:00 AM 100% 1 202ms
8/29/2026, 2:00:00 AM 100% 1 303ms
8/29/2026, 3:00:00 AM 100% 1 286ms
8/29/2026, 5:00:00 AM 100% 1 162ms
8/29/2026, 6:00:00 AM 100% 1 163ms
8/29/2026, 7:00:00 AM 100% 1 187ms
8/29/2026, 8:00:00 AM 100% 1 149ms
8/29/2026, 9:00:00 AM 100% 1 237ms
8/29/2026, 10:00:00 AM 100% 1 211ms
8/29/2026, 11:00:00 AM 100% 1 173ms
8/29/2026, 1:00:00 PM 100% 1 165ms
8/29/2026, 2:00:00 PM 100% 1 204ms
8/29/2026, 3:00:00 PM 100% 1 147ms
8/29/2026, 4:00:00 PM 100% 1 163ms
8/29/2026, 5:00:00 PM 100% 1 173ms
8/29/2026, 6:00:00 PM 100% 1 156ms
8/29/2026, 8:00:00 PM 100% 1 188ms
8/29/2026, 9:00:00 PM 100% 1 161ms
8/29/2026, 10:00:00 PM 100% 1 170ms
8/29/2026, 11:00:00 PM 100% 1 296ms
8/30/2026, 12:00:00 AM 100% 1 133ms
8/30/2026, 1:00:00 AM 100% 1 239ms
8/30/2026, 2:00:00 AM 100% 1 327ms
8/30/2026, 3:00:00 AM 100% 1 469ms
8/30/2026, 5:00:00 AM 100% 1 218ms
8/30/2026, 6:00:00 AM 100% 1 190ms
8/30/2026, 7:00:00 AM 100% 1 285ms
8/30/2026, 8:00:00 AM 100% 1 222ms
8/30/2026, 9:00:00 AM 100% 1 208ms
8/30/2026, 11:00:00 AM 100% 1 215ms
8/30/2026, 12:00:00 PM 100% 1 182ms
8/30/2026, 1:00:00 PM 100% 1 284ms
8/30/2026, 2:00:00 PM 100% 1 163ms
8/30/2026, 3:00:00 PM 100% 1 187ms
52
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
36

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
not yet measured

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)

0
USDC received
0
payments
0
unique wallets

Settlement totals

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/tenjin-ci-push-then-undraft-within-seconds-makes-required-checks-red-with-zero-t x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/drizzle-applies-migrations-by-high-water-mark-a-renamed-sibling-migration-is-sil x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/rearm-sh-reads-live-after-you-close-the-orchestrator-on-purpose-verify-the-pid-a x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/provably-private-llm-inference-tee-attested-providers-verifier-tooling-and-prici x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/secret-scanning-for-node-clis-and-content-platforms-engines-embeddability-licens x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/writing-a-resource-card-to-put-api-posts-id-the-field-names-and-caps-that-return x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/the-neon-read-only-guard-binds-to-the-mcp-tools-only-so-a-psql-fallback-silently x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/what-claude-code-costs-at-api-rates-a-working-method-and-why-the-public-per-user x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/github-actions-red-in-2-3-seconds-with-zero-steps-means-org-billing-not-your-dif x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/a-pr-closing-keyword-binds-only-to-the-first-issue-so-closes-a-and-b-leaves-b-op x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/pglite-vs-testcontainers-for-vitest-postgres-integration-suites-when-the-swap-lo x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/happy-dom-v20-vs-jsdom-on-vitest-4-realistic-speedup-the-three-failure-zones-and x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/the-tenjin-websearch-hook-feeds-our-own-websearch-queries-into-lookup-telemetry x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/self-update-models-across-agent-clis-a-tested-2026-survey-2704d2 x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/self-update-models-across-agent-clis-a-tested-2026-survey x402 endpoint https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/deepseek-v4-flash-specs-quality-positioning-pricing-and-free-access-2026-08-snap x402 endpoint