Snapshots: Jun 15 10.0 Apr 24 launch 7.1

← Back to browse

Siebly.io, Crypto APIs made easy for AI claimed

Use the Siebly Prompt Framework with Codex, Claude Code, and Cursor to build Binance, Bybit, OKX, and other crypto exchange API integrations with maintained Node.js and JavaScript SDKs.

AI

Added April 24, 2026 · Last analysed June 15, 2026 · via PeerPush · 62% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 15 June 2026; the live site may have changed since.

Siebly.io, Crypto APIs made easy for AI ships with the launch fundamentals in place, with complete legal pages, a complete set of security headers, and a thorough launch checklist. What needs work: incomplete email security.

Launched on PeerPush on April 24, 2026. The site is served through Cloudflare. The crawl picked up 15 technologies on this site, covering developer tools, tag management, advertising, and analytics. The stack includes Tailwind CSS, Cloudflare, and Cloudflare DNS.

For context, it's running the same core stack as 5,948 other launches and tighter on security headers than most PeerPush launches.

Owner tools →

10.0
StackScope Score
Excellent
100/100 Launch Readiness
Launch ready
3/3 Legal
Complete
2/2 Crawl files
Complete
Vibe Score 10 · Few AI signals
How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (15)

Infrastructure
CDN Cloudflare
DNS Cloudflare DNS
Protocol HTTP/3
Security HSTS new
Email
Business email Google Workspace (2)
Build & Framework
CSS framework Tailwind CSS
Developer tools npm new
Vite
UI library shadcn/ui
Analytics & Marketing
Advertising Google Ads new
Analytics Google Analytics (2)
Publishing Substack new
SEO Google Search Console
Tag management Cloudflare Zaraz
Google Tag Manager new

Infrastructure

Network
AS13335 · US
DNS
Cloudflare DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Google Trust Services
Valid 27 May 2026 to 25 Aug 2026
Certificate as captured in this snapshot, not a live check.

Email Security

SPF -all Strict (-all). Strong.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC Not published. Receivers fall back to permissive defaults.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (2)

Cookies (2)
NameLifetimeDetected as
cfzs_google-analytics_v4 session Cloudflare Zaraz
cfz_google-analytics_v4 12mo Cloudflare Zaraz

Readiness Breakdown How?

Custom title and meta description
Open Graph tags (title, image, description)
Twitter card meta tags
Canonical URL declared
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
Page title is 67 characters (advisory) Google only shows about 60 characters of the title in search results; aim for 50–60 to keep the whole thing visible.
Meta description is 185 characters (advisory) Google only shows about 155–160 characters of the description in desktop search results (less on mobile); anything past that won't appear.

Performance How?

268 ms Server response
61% Faster than peers
852 ms Largest contentful paint
0.00 Cumulative layout shift
418 KB Page weight
8 KB Image weight
2 Third-party domains
0 Console errors
0 Failed requests

4 images: 4 oversized, 1 without width/height, 1 missing alt text

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

Vibe Score Breakdown How?

SignalPoints
AI palette signals +5
AI layout signals +5

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

AI Stance

Welcomes AI crawlers
llms.txt published
No AI bots blocked in robots.txt
ai-train = yes
search = yes
ai-input = yes
service-doc

Well-Known Files

robots.txt
sitemap.xml (34 URLs)
security.txt
llms.txt
ads.txt
humans.txt
Privacy Policy
/privacy
Terms of Service
/terms
? Analytics present, but it set no tracking cookies on our visit (it may be opt-in-gated).
92% unique

Security Headers (6/6)

Permissions-Policy experimental (check browser support)
Content-Security-Policy ⚠ CSP violation detected: your policy is blocking 1 of your own resource
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

2 JS files
1 CSS files
2 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.