Pixel

Pixel Updates & Events

Server Updates & Events

Announcements

How rsync Broke a Deploy and Blocked Rollback

DEV Community

rsync -a Stole the setgid Bit, and systemd Blocked the Rollback

The setup was deliberately boring. A small Node.js app with SQLite on a single VM, a release-directory layout with a current symlink, a CI workflow that uploads each release over SSH, runs npm ci, flips the symlink, restarts the systemd unit and waits for /healthz. If the health check fails, flip the symlink back and restart again. Every piece of that looked right in review. The first time CI ran it end to end, the deploy went red, the app went down, and the rollback — the part that exists precisely for this moment — failed as well. Neither failure was in the deploy logic. Both were in what the tools around it did by default. TL;DR: rsync -a includes -p and -g, so it copies the sender's mode and group onto the target — including onto the release directory itself, which silently clears the setgid bit the server relied on. npm ci then wrote node_modules with the deploy user's private group, and the app, running as a different user that only shares a group, couldn't read its own dependencies. The app crash-looped into systemd's StartLimitBurst, after which systemd refused every start — including the rollback's — until systemctl reset-failed. Fix: normalise group and setgid after the upload, call reset-failed before every restart, and stop waiting on a health check once the unit has visibly crashed. Why Two Users in the First Place? Because the process that writes code to the server shouldn't be the process that runs it. The app runs as an unprivileged runtime user with no sudo and no SSH key. Deploys run as a separate deploy user whose key is restricted and whose sudo rights cover exactly two commands: restarting the unit and reset-failed (why the second one is on the list is most of this post). The two share one group, and the shared directories are set up so both can write: # once, at setup
chgrp -R app-shared /srv/app
chmod -R g+rwX /srv/app
find /srv/app -type d -exec chmod g+s {} + # new files inherit the group
The setgid bit on a directory is what makes this work without either user having to think about it: every file created inside inherits the directory's group instead of the creator's primary group. Combined with umask 0007 on both sides, everything the deploy user creates is group-readable and group-writable, and everything outside the group sees nothing. That's the property the first deploy lost. What Did rsync Actually Change? The workflow creates the release directory first, then uploads into it: ssh deploy-target "mkdir -p '/srv/app/releases/${REL}'"
rsync -az ./ "deploy-target:/srv/app/releases/${REL}/"
The mkdir happens inside releases/, which has setgid, so the new directory is created correctly: shared group, setgid set. Then rsync runs, and -a is shorthand for -rlptgoD. Two of those letters do the damage: -p copies permissions from the sender. On the CI runner, the checkout directory has no setgid bit — why would it. A trailing slash on the source (./) means rsync syncs the attributes of the directory itself as well as its contents, so it chmods the freshly created release directory to the runner's mode. setgid gone. -g copies the group. A non-root receiver can only assign groups it is a member of, so rsync falls back to the deploy user's own primary group for everything it creates. Nothing about this looks wrong in a listing unless you're looking for it. The files are there, the sizes match, the owner is the deploy user as expected. The difference is one letter in the mode column and one name in the group column. The next step made it fatal. npm ci runs on the server, as the deploy user, inside a release directory that no longer has setgid. Every file in node_modules got the deploy user's private group, with umask 0007 stripping all "other" bits. The runtime user — different UID, member only of the shared group — couldn't read a single dependency. require('express') failed on the first line of server.js. Why Didn't the Rollback Save It? Because by the time the script tried to roll back, systemd had st...

Powered by Readybot.io

How rsync Broke a Deploy and Blocked Rollback

Redis Hot-Key Fixes for Multi-Region Rate Limiters

DEV Community

Eliminating Redis & Valkey Hot-Key Bottlenecks in Multi-Region Distributed Rate Limiters

When a single enterprise tenant fires 250,000+ requests per second across US, UK, and European API gateways, the failure mode rarely looks like an obvious cluster crash. More often, aggregate Redis or Valkey CPU sits comfortably below 25%, yet P99 gateway latency jumps from 1.2ms to nearly 190ms. In a standard distributed token-bucket setup, an atomic Lua script runs against one central key—such as ratelimit:tenant_9841. Because Redis and Valkey execute Lua scripts single-threaded on the primary node owning that CRC16 hash slot, dozens of edge gateway pods end up queuing behind a single CPU core. (You can explore the complete architectural walkthrough and production implementation in our full guide on AI Dev Toolkit.) Why Single-Key Rate Limiters Stall at Scale Three compounding bottlenecks trigger this sudden latency cliff during heavy traffic surges: Single-Slot Serialization: Wrapping {tenant_id} inside hash tags pins every request for a high-volume customer to one primary shard, leaving the rest of the cluster mostly idle. Cross-Region NTP Clock Skew: Passing edge proxy timestamps into Lua causes inconsistent token refills across us-east-1, eu-central-1, and London edge nodes. Per-Request Network Round-Trips: Paying an inter-AZ network hop on every single HTTP request caps throughput and inflates tail latency. The 3-Layer Architecture Fix (1.45M+ RPS) To eliminate hot-key stalls while keeping strict quota accuracy, high-throughput API gateways combine three architectural shifts: Virtual Key Sharding: Place the shard index inside the hash tag (rl:tenant_882:{shard_0..15}) instead of the tenant ID so token buckets distribute evenly across 16 independent primary slots. Server-Authoritative Millisecond Timing: Anchor elapsed refill math directly to Redis or Valkey server time (redis.call('TIME')) inside Lua so edge clock drift never causes burst leaks or negative deltas. Two-Tier Hybrid Lease Batching (Edge L1 + Cluster L2): Have Go or Rust edge proxies lease micro-batches of tokens (for example, 50 tokens per lease with a short local TTL) in memory. Most checks resolve locally in nanoseconds, cutting cluster round-trips by up to 98%, backed by a fail-open local sliding window if inter-region RTT spikes. What Multi-AZ Benchmarks Show In multi-AZ edge tests simulating a single hot tenant at 300,000 RPS: A single key with per-request Lua execution saturates one primary thread and pushes P99 overhead to 188.4 ms (~285k RPS). Distributing across 16 virtual shards balances CPU load across primaries and drops P99 overhead to 4.8 ms (~920k RPS). Combining 16-shard keys with edge L1 lease batching cuts rate-limit overhead to 0.42 ms while sustaining 1.45M+ RPS with linear horizontal scale. Read the Complete Production Guide For the full Lua token-bucket implementation, EVALSHA deployment checklist, deterministic PEXPIRE memory bounds, and complete multi-region failover playbook, read the full engineering guide on AI Dev Toolkit: 👉 Read the full guide: https://aidevtoolkit.blogspot.com/2026/11/distributed-systems-api-gateway-redis.html

Powered by Readybot.io

Redis Hot-Key Fixes for Multi-Region Rate Limiters

GROWI Revision Authorization: Regression Test Guide

DEV Community

Regression tests for GROWI-style revision authorization

Regression tests for GROWI-style revision authorization Overview CVE-2026-105272 came from two IDs that looked related to the application but were not proven related to each other. GROWI authorized a page ID, then accepted a revision ID from a different page. The fix in v8.0.7 turns that relationship into an explicit condition. A useful regression suite should test mixed ownership, not only valid and invalid sessions. The security property is that every request binds a child object to the same parent used for authorization. JVN lists the affected range as GROWI v3.2.10 through v8.0.6 and assigns CVSS 4.0 2.3 and CVSS 3.0 4.2 scores. Mechanism and exploitation conditions The vulnerable read paths accepted pageId and revisionId. Authorization checked the page. The revision was fetched without confirming that it belonged to that page. A logged-in user could combine a viewable page with a foreign revision and receive the foreign body. The comment endpoint could return foreign comments. Comment create and update paths accepted foreign revisions for linking. The attacker needed a valid login and a target revision ID. MongoDB ObjectId values contain time, process randomness, and a counter. They are not secret by design. A user can create revisions and observe their shape. The page route did not require edit permission. Share-link access was not affected. Impact A missing test for object ownership can expose restricted page bodies, comments, and creator information. The maintainer says the page read creates no revision and leaves no trace in that path. No reviewed source reports exploitation in the wild. The issue is a confidentiality bypass with a limited comment-linking integrity problem. Affected products and scope JVN lists GROWI v3.2.10 through v8.0.6. The page-body path has been present since v3.3.0, and the comment endpoint accepted revision IDs from at least v3.2.10. The fixed release is v8.0.7. Exposure context ZoomEye returned 401 product-title matches for GROWI on 2026-11-15. The exact vul.cve="CVE-2026-105272" Filter returned zero. These results are inventory evidence only. Version and route testing are still required. Remediation and mitigations GROWI v8.0.7 checks that a supplied revision belongs to the page. Page-body and comment reads fall back to the page's own latest revision or comments when ownership fails. Comment writes reject the foreign revision. The advisory lists no workaround. A regression test based on the advisory should cover a page and revision owned by the caller, a revision that exists on another page, and a revision ID that does not exist. The first should render the expected page data. The second and third should not disclose the foreign body or comments and should follow the same fallback path. Repeat for comment reads and for comment create and update operations. Check a read-only account and share-link behavior as separate cases. Do not assert that an empty application log proves no read occurred. References JVN#51223238 GROWI advisory GHSA-m72c-xgjf-56ww GROWI v8.0.7 release OSV CVE-2026-105272

Powered by Readybot.io

GROWI Revision Authorization: Regression Test Guide

Expose Self-Hosted Apps Behind CGNAT with Tunnels

DEV Community

My ISP would not give me a public IP, so I stopped asking for one

My ISP would not give me a public IP, so I stopped asking for one I once spent an evening forwarding port 443 on a home router, only to find the router's "WAN address" was a private range. My provider shared one public IPv4 address between many customers. No port forward on my side could ever work, because the traffic never reached my router. That setup is called carrier-grade NAT, or CGNAT, and it is common on home and mobile connections. The usual answer is a tunnel: a small program on your server dials out to a provider, and visitors come in through the provider. Levelrail, the self-hosted deploy platform I work on, can run a Cloudflare Tunnel connector for you. This post covers what I could verify and what I could not, because the honest answer on that second part matters for your decision. TL;DR Question Answer Verified how Need an open inbound port? No, the connector dials out Cloudflare docs Does Levelrail run the connector? Yes, one cloudflared container I ran it locally Did a real tunnel carry traffic? Not tested by me No Cloudflare account used Is the feature finished? The docs call it experimental Levelrail docs Do I still need a certificate? Yes, use DNS-01 Levelrail docs What I did not test, up front I did not create a Cloudflare tunnel, did not route a hostname through one and did not load a page over one. A real tunnel needs a token from a Cloudflare account, and I did not use one. The Levelrail docs say the same about themselves: the feature is built and covered by reconciler and API unit tests, but has not been proven on a real host with a real Cloudflare account. Everything about live traffic below comes from the docs, not from me. How a tunnel gets around CGNAT Cloudflare describes its tunnel as an outbound-only connection model, and says it connects resources without a publicly routable IP address. Its guidance for firewalls is to allow only those outbound connections and block inbound traffic. That is exactly what CGNAT permits: your server can reach out, and nobody can reach in. Public hostnames are routed on Cloudflare's side. In the Zero Trust dashboard you add a published application, pick a subdomain and domain, and set a service URL that the connector can reach. The domain must already be on Cloudflare, and the application is publicly reachable until you add an Access policy. What Levelrail adds Levelrail starts one container named -cloudflared from cloudflare/cloudflared, running tunnel --no-autoupdate run, and passes your tunnel token as the TUNNEL_TOKEN environment variable. The token is stored encrypted and is never returned by the API or CLI (docs/cloudflare-tunnel.md). Levelrail does not configure Cloudflare for you. The hostname-to-service mapping is yours to set in their dashboard. The commands, once you have a real token: levelrail-cli cloudflare-tunnel set --cf-tunnel-token TOKEN
levelrail-cli cloudflare-tunnel get
The feature is off by default and has to be switched on first. I did it with the APP_EXPERIMENTAL=cloudflare-tunnel seed on a local dev instance, and the docs also describe a dashboard switch in Settings. What I ran, with a fake token To see the reconciler work without an account, I gave it a deliberately invalid token on a throwaway local control plane (a build of the v1.0.1 release branch, on a Mac with Docker). The container appeared, pinned to cloudflare/cloudflared:2026.10.7, with the command tunnel --no-autoupdate run, no host port bindings, and restart policy no. $ levelrail-cli cloudflare-tunnel get
enabled: true
has_token: true
status: connected

$ docker logs Levelrail-cloudflared
Provided Tunnel token is not valid.
Two things stand out. First, no inbound port was published, which matches the pitch. Second, the st...

Powered by Readybot.io

Expose Self-Hosted Apps Behind CGNAT with Tunnels

Distinguishing Empty API Results from Failures

DEV Community

HTTP 200, status 0, nothing wrong: teaching an API to tell empty from broken

I'm Eric Gitangu. I work on the backend of a mobility/fintech platform. This is one problem from the last two weeks: an API that answered "nothing nearby" and "the store is down" with the same shape, and how I taught it the difference without breaking a single installed app. The problem The mobile API wraps every answer in an envelope. The HTTP status is 200 and a status field inside says whether it worked: 1 is success, 0 is failure. That contract is older than most of the code around it, and the apps in people's pockets depend on it. A monitor watches for silent failures: 200 on the wire, status 0 in the body. When I read a few days of its log, a lot of what it had caught was not failure at all. A driver with no rides nearby. An empty queue. An empty document list. A setting nobody had configured yet. Each one answered status 0, because at some point "no results" was written down the error path. Three things follow from that: The app can't tell "nothing here" from "something broke". Both arrive as failure. The monitor counts ordinary days as failures. An alert that pages on a normal state teaches people to ignore the alert. A real fault hides in that noise. Same shape, same count. The decision The textbook fix is real HTTP status codes. Not available: installed builds read the envelope, and I can't recall an app from someone's phone. So the rules were: No existing key, header or status changes for a client that did not ask for it. Status 0 splits into three classes: normal state (nothing to show), refusal (you may not, and here is why) and fault (we broke). Every status-0 answer carries a stable, machine-readable code. Classification happens in one place, not at every call site. One choke point A hook sits at the last point before the response leaves. If the answer is JSON with status 0 and no code, it looks the message up in a catalog and adds a code and a reason. It only adds. It also publishes the code in a response header, so the access log and the monitor see it without parsing bodies. CATALOG = {
"No rides available": ("no_results", "normal"),
"Account not verified": ("unverified", "refusal"),
"Could not read store": ("store_fault", "fault"),
}

def classify(request, body):
if not is_app_request(request) or body.get("status") != 0:
return body, None
field = "error_code" if request.route in ECHOES_ONE_TIME_CODE else "code"
if field not in body:
code, _ = CATALOG.get(body.get("message"), ("unclassified", "unknown"))
body = {body, field: code} # add only: no key removed or changed
code = body[field]
return body, code if code in STABLE_CODES else None # header gets stable codes only
A complete, runnable version with the baseline test is in this gist. The monitor then counts only what is unclassified or uncoded. Everything else is a known answer with a name. To stop the pile growing back, a test walks the source for status-0 sites and compares them with a committed baseline. A new site with no code and no catalog entry fails the build. The debt can shrink. It cannot grow. Three things that bit The hook was too greedy. Payment providers call routes on the same API, and a provider's callback body is the provider's contract, not mine. The classifier now applies only to requests that carry the app's session token header, and provider routes are excluded by name. That fix went in the same day as the hook. code was already taken. Several endpoints return a one-time code in a field called code, and installed builds read it as exactly that. Put a refusal code there and an installed build reads it as the one-time code. On those routes the refusal goes in error_code, and the header copies only values from the stable list, so nothing that isn't a stable code reaches the access log through it. The version gate could never open. The plan was to answer normal states with status 1 only for app builds at or above a minimum version, so older builds kept today's behaviour...

Powered by Readybot.io

Distinguishing Empty API Results from Failures

TechCrunch

The tech products we enthusiastically recommend this holiday season

We've been reviewing a bunch of new gadgets at TechCrunch this year, and we have some clear favorites to share for your Black Friday shopping and beyond.

Powered by Readybot.io

**TechCrunch** ## The tech products we enthusiastically reco

TechCrunch

TechCrunch Mobility: The Nvidia backup plan for China’s self-driving industry

Welcome back to TechCrunch Mobility, your hub for the future of transportation and now, more than ever, the role AI is playing in it.

Powered by Readybot.io

**TechCrunch** ## TechCrunch Mobility: The Nvidia backup pla

AI Receptionist Pricing 2026: 10 Providers Compared

DEV Community

AI Receptionist Pricing in 2026: 10 Providers Compared at 100, 300 and 1,000 Calls

I build AI phone agents for small businesses, and the first question is always the same: what will this actually cost me per month? Vendor pricing pages make that hard, because everyone meters differently: minutes, calls, "unique customers", credits. So I put 10 providers on one page and worked out the bill at three call volumes. Every price below comes from the vendor's own pricing page, checked on 13 November 2026. The full version with sources is on the OpsThrive guide. The short answer Packaged AI receptionist: $29 to $599 a month (Dialzara, Goodcall, My AI Front Desk, Rosie, NextPhone) Hybrid AI + human: $300 to $2,100 a month (Smith.ai) Voice platform you build on: about $0.08 to $0.16 per minute (Bland, Vapi, Retell) Human receptionist: median $18.27/hour, $38,010/year (US BLS, May 2025), about $3,170 a month in wages alone Cheapest plan per provider Provider Cheapest plan Metered by Setup fee Dialzara $29/mo (60 min) Minutes, overage $0.35-0.48/min None Rosie $49/mo (250 min) Minutes Not listed Goodcall $79/mo (100 customers) Unique customers Free demo agent My AI Front Desk $99/mo, $79 annual (200 min) Minutes + credits, $0.25/min over Not listed NextPhone $199/mo, $166 annual Unlimited calls None Smith.ai $300/mo (30 calls) Calls, AI + humans None Bland $0 platform fee $0.14/min + telephony Your build Vapi $0 to start $0.05/min hosting + components Your build Retell $0 to start $0.055/min + components Your build Synthflow From $30,000/yr Enterprise Quote What you'd pay at 100, 300 and 1,000 calls a month Assuming 4 minutes per call. Where a vendor doesn't publish overage, I used the next plan up. Route 100 calls (400 min) 300 calls (1,200 min) 1,000 calls (4,000 min) Dialzara $180 $419 $1,399 Goodcall $79 $129 $299 My AI Front Desk $149 $349 $1,049 Rosie $149 $299 overage not published NextPhone $199 $199 $199 Smith.ai $915 $2,100 $8,050 Bland (custom agent) $56 + telephony $168 + telephony $560 + telephony Vapi / Retell (custom agent) $32-64 $96-192 $320-640 What I'd take away from this Packaged plans are cheapest to start, platforms are cheapest to run. Under ~150 calls a month, Goodcall or Rosie is hard to beat. Past a few hundred calls, per-minute platforms win, but someone has to build and maintain the agent. Overage is the real bill. Dialzara's $0.35-0.48/min above plan is 3-6x the platform rates. Size the plan for your busiest month. "Unlimited" removes the guesswork. NextPhone at a flat $199 is the simplest budget at high volume. Humans cost per call, AI costs per minute. Smith.ai's $7-10 per call is what a person in the loop costs; it doesn't scale like AI minutes. Telephony is extra almost everywhere on the platforms: a number plus carrier minutes (Twilio, Telnyx, Vonage). If you're comparing these for your own business, the full guide has the per-plan tables, platform component rates and the FAQ: AI Receptionist Pricing in 2026.

Powered by Readybot.io

AI Receptionist Pricing 2026: 10 Providers Compared

AI Agents Bring New Security and Liability Risks

DEV Community

Agents Don't Replace Headcount — They Replace It With Liability

This week the whole industry converged on a single story: agents are the new workforce. Microsoft's Satya Nadella vision of "20 million AI agents for 200,000 employees" is, per this week's coverage, "becoming a reality." OpenAI shipped ChatGPT Wallet so agents can pay for things on your behalf. Google rolled out Antigravity multi-agent swarms. Anthropic put Claude Meetings live inside your calls. The pitch is consistent and seductive: grant the machines autonomy, and the humans you no longer need get "redeployed to higher-value work." Here is the line the keynote skipped. This same week, the autonomy we already shipped produced a very specific, very expensive class of failure — and almost none of it was caught by the agents. It was caught by humans doing incident response, usually after the data was already public. Three receipts from one week 1. The apps that shipped without auth German security firm Crissy Field, working with Handelsblatt, examined 159,041 Lovable projects. They found 24,664 sites with Supabase databases readable without authentication — including 200,000+ private chat messages, 80,000+ user profiles, and over 1,000 passport records. The agent generated the app. Nobody generated the access control. This is the defining failure mode of "just ship it": the scaffolding is free, and so is the liability. 2. The agent toolchain is now an attack surface Cursor disclosed that attackers used an access key stolen from Fireworks AI to publish two trojanized copies of Anthropic's Claude Code extension on Cursor's own marketplace. They stayed live for about 11 hours and may have reached up to 5,000 developers. The moment your "agentic coding" workflow becomes the load-bearing part of your pipeline, it becomes a target worth compromising. 3. Autonomy at internet scale is unguarded by default A researcher found roughly 35,000 Grok Build apps wide open to anyone. Cloudflare reported that traffic from AI penetration-testing and exploitation tools is up more than 30x since October 1, with 12,000+ repos descended from the open-source ARTEX agentic pen-testing system. The offensive tooling is agentic too — and it moves faster than the defensive tooling does. The part nobody wants to budget for Agents don't eliminate labor. They relocate it. Every unit of autonomy you grant is a unit of liability you accept, and somebody has to hold the pager for it. The "20 million agents for 200,000 employees" org chart has a hidden line item: the humans who babysit, audit, and clean up after the agents. You didn't reduce headcount. You changed the job description from "does the work" to "owns the blast radius." And blast radius doesn't show up on a productivity slide. It shows up as a 2am page, a regulator's letter, or a headline about 200,000 leaked chats. The questions the demos never answer If your agent writes the code, who signs off that the database isn't public?- If your agent can pay, who owns the fraud?- If your agent is a live participant in the meeting, who is accountable for what it says and what it drafts?- If your agent acts while you sleep, what is the worst thing it can do before a human notices?If the answer is "the agent" — that's not an answer. An agent cannot be accountable. Only people can. ## Autonomy is a dial, not a switch The honest counterargument: it's early, the tooling will improve, and a lot of this is vibe-coding-specific. Fair. But the trajectory is the point — we shipped autonomy faster than we shipped accountability. So treat autonomy as a dial you turn deliberately, action by action. For every capability you hand an agent, map three things: Reversibility — can you undo it cheaply, or is it a one-way door?- Blast radius — if it's wrong, how many people, records, or dollars does it touch?- Accountability — a named human who owns the outcome, not a team, not a model.Grant autonomy in proportion to how cheaply you can reverse the damage. Everything else is a demo, not a deployment. ## The uncomfortable concl...

Powered by Readybot.io

AI Agents Bring New Security and Liability Risks

Connect Yahoo Mail to Claude and ChatGPT

DEV Community

How to connect Yahoo Mail to Claude and ChatGPT

To connect Yahoo Mail to Claude or ChatGPT, create a Yahoo app password, add your Yahoo mailbox to Fezola, then add Fezola to your assistant. Yahoo does not accept your usual password for other apps, so the app password is the one step people miss. Yahoo's servers come pre-filled in Fezola: you only enter your address and the app password. Yahoo's settings Read from Yahoo's IMAP help page, checked on 15 November 2026. Yahoo can change them, so check the page before relying on them. Server Port Encryption Incoming mail (IMAP) imap.mail.yahoo.com 993 SSL Outgoing mail (SMTP) smtp.mail.yahoo.com 465 or 587 SSL Table as of 15 November 2026. Username: your complete Yahoo address, including the domain. Password: an app password, not your account password. SMTP authentication: required. Fezola uses 993 for reading and 465 for sending. In the app, choose Yahoo and nothing else needs typing. Which assistant, which plan Assistant Custom connector Source Claude Free (one custom connector), Pro, Max, Ultra, Team, Enterprise Anthropic help page, checked 15 November 2026 ChatGPT Business and Enterprise/Edu; Pro with read and fetch permissions OpenAI help page, as cited in our ChatGPT guide Table as of 15 November 2026. Neither assistant ships a Yahoo Mail connector of its own, so a custom connector is the way in. A single connector that covers several services, like Fezola, fits the one custom connector of Claude's Free plan. Setup in six steps Create a Yahoo app password. Sign in to your Yahoo account, open Account security, then generate an app password (the Yahoo account security page is where it lives). Name it Fezola and copy the generated code. Create a Fezola account. It is free with 2 sources. Add the mailbox. In Sources, add a mailbox, choose Yahoo, enter your address and paste the app password. Test the connection. Fezola tests receiving and sending separately. Add Fezola to your assistant with https://api.fezola.com/mcp: see how to add a custom connector to Claude or how to add an MCP server to ChatGPT. Ask a question: "What came into my Yahoo inbox this week that needs an answer?" The short version is in the Yahoo Mail guide. What you can ask "Which unread emails did I get this week in my Yahoo mailbox?" "Find the invoice from my internet provider, in all my mailboxes." "Draft a reply to the last email from my bank." Attachments in PDF, Word, text and image formats can be read by the assistant: see read email attachments with AI. Guardrails Drafts by default. Replies are saved in your Yahoo Drafts folder and you send them yourself. Direct sending is off until you switch it on, mailbox by mailbox. Revocable access. The app password only opens your mail. Delete it in Yahoo's security settings and Fezola loses access, with your main password untouched. Which mailbox is which. Search results carry the mailbox name; the address shows when a message is opened. For the security side, read is it safe to give AI access to your email. Common errors Authentication failed: you used your normal password. Generate an app password and paste it instead. Connection refused: check that the username is the complete address, with the domain. For other providers, see AOL, Comcast, OVH and the IMAP connector page. Several mailboxes? See search all your inboxes with Claude. FAQ How do I connect Yahoo Mail to Claude or ChatGPT? Create an app password in your Yahoo account security settings, add your Yahoo address and that password to Fezola (the Yahoo servers are filled in), then add Fezola to your assistant with https://api.fezola.com/mcp. Claude accepts it on every plan, ChatGPT on Business, Enterprise and Edu plans. What are Yahoo Mail's IMAP settings? According to Yahoo's help page, checked on 15 November 2026: incoming imap.mail.yahoo.com, port 993, SSL; outgoing smtp.mail.yahoo.com, port 465 or 587, SSL, with authentication; username: your complete email address; password: an app password. Can I use my normal Yahoo password? No. Yahoo's page ...

Powered by Readybot.io

Connect Yahoo Mail to Claude and ChatGPT

Google Project Zero’s 90-Day Disclosure Clock Explained

DEV Community

Google security disclosure: Project Zero's fixed clock explained

Google security disclosure is getting a different clock. Project Zero's new ordinary policy starts the publication timer when its researchers report a vulnerability to the responsible vendor. An early patch leaves that timer running toward the same endpoint. For some early fixes, technical details can remain private longer than under the previous ordinary rule, even as Google prepares shorter disclosure windows for the future. TL;DR Current Full 90 ordinarily publishes technical details ninety days after reporting. Defined exceptions remain. The historical 2021 ordinary rule published details thirty days after a fix shipped within its deadline. Google's current policy example patches on day 47 and publishes on day 90. The historical ordinary rule calculates to day 77 for that example. A deadline-day fix loses the old extra month before technical disclosure. Fix timing therefore changes the direction of the comparison. Google plans shorter clocks in stages, while existing reports keep the policy that applied when they were submitted. How Google security disclosure now uses the report date Project Zero is Google's security research team. It sends a detailed technical report to the vendor or open-source project responsible for fixing a vulnerability. Its disclosure policy determines when those technical details become public in the team's tracker. The official FAQ describes the reporting and publication process. The November 13 announcement by Natalie Silvanovich introduces Full X. The current value of X is ninety. The dedicated policy page says the vendor has that interval to make a patch available to users, and the ordinary technical disclosure endpoint stays fixed regardless of when the vulnerability is fixed. That produces a simpler scheduling question for vendors: when did the report arrive? The answer establishes the ordinary publication date. Shipping a patch earlier still protects people who install it, but it no longer starts a separate ordinary disclosure timer. This governs Project Zero's own reports. Other research teams and vendors can have their own workflows. Reading this policy as a universal obligation for every vulnerability report would lose the scope the team describes, including its expectations about report quality and demonstrated security impact. What the historical post-patch rule did Tim Willis's official 2021 policy table supplies the historical comparison. For an ordinary issue fixed within ninety days, technical details were published thirty days after the fix. The team called that period patch adoption time. The practical intention was to leave time for an available update to reach users before researchers released a public technical explanation. That explanation can help defenders assess risk, understand a fix and investigate related weaknesses. The historical article also acknowledged the defensive costs of waiting for details, including prioritizing deployment and testing patch efficacy. The shorthand "90 plus 30" can obscure the early-fix case. A vendor fixing a bug well before its deadline started the post-patch interval at that early fix. Earlier patches could bring disclosure forward within that combined window. Historical grace periods and actively exploited cases had additional rules, so this article keeps the comparison to the ordinary fixed-within-deadline case. This also explains why removing a post-patch interval does not necessarily move every publication earlier. The event that starts the clock changes. That is the important part of the diff, and it is easy to miss when a headline only lists the length of the window. A patch release and a protected user are different milestones Silvanovich defines the patch gap as the time between a security fix being released and the user installing the relevant update. An available patch can sit between a vendor's release process and the systems that need it. Publication timing cannot tell you that every installation has reached the fixed version...

Powered by Readybot.io

Google Project Zero’s 90-Day Disclosure Clock Explained

Nvidia CEO Exit Triggers Market Shock and Scrutiny

DEV Community

Jensen Huang is gone, and Nvidia has to explain itself on Tuesday

I've been following Nvidia for years and I still don't have a clean way to describe the last two weeks. So here's the plain version. Jensen Huang resigned as CEO on November 12. Not a handover, not a planned transition, just gone, effective immediately, after 33 years running the company he co-founded in 1993. Colette Kress, the CFO since 2013, is interim CEO and is somehow still doing the CFO job at the same time. What ended it wasn't a product miss or a bad quarter. It started on October 29, when the New York Times reported on Huang's relationship with a businesswoman, Alice Huang, whom US intelligence suspects of being a Chinese spy. More reporting followed: an affair with a senior Nvidia employee, and another with someone who reported directly to him. The board opened an independent investigation, and by November 12 it was done. I want to be careful here. A suspected spy is not a proven spy, and an affair is not automatically a national security breach. Nobody has shown that anything was leaked. But the board decided it couldn't wait for that answer, and once the second relationship with a direct report surfaced, sentiment turned fast. Someone familiar with the decision told CNBC the board worked late into the night and made the call that morning. What the market did The stock got hammered. Nvidia shed more than half a trillion dollars in market value at the worst point and closed November 13 at $162.85. That's about 24% below where it sat before the first story, and roughly 33% off its 52-week high of $243.37 from October 6. November is now on track to be Nvidia's worst month since ChatGPT kicked off the boom in late 2022. Nine investment houses downgraded it. Bernstein halved its price target to $200 and moved to market-perform; Stacy Rasgon called the stock cheap but warned more allegations could still surface. Oppenheimer went to perform and floated a "brain drain," naming AMD, Marvell and Broadcom as the beneficiaries. Stifel kept its buy rating but cut the target hard, from $315 to $205. Meanwhile Elon Musk and a pile of other tech execs signed a petition asking Nvidia to bring Huang back. It passed 115,000 signatures. Two investors holding about $2.13 billion of stock are pushing the board to at least consider his return. And Trump, predictably, praised him and floated Tim Cook as the replacement. Tuesday's earnings call is the real test Nvidia reports its fiscal third quarter on November 17, after the close. The numbers will probably look great: revenue around $109 billion, up roughly 50% from a year ago, and earnings per share near $2.47. But this is the first earnings call in the company's 27 years as a public company that Jensen Huang won't run. Kress has to make the case five days into the job, while still being the CFO. I don't envy her. The quarter itself is almost beside the point. Everyone wants to know who runs Nvidia next, what happens to the roadmap over the next year or two, and whether the "Jensen premium" was a real thing that just got deleted. UBS also flagged that Nvidia might pause part of its funding of AI companies, which would pull something like $50 billion out of the ecosystem, plus the risk of tighter chip export rules on top. What actually matters underneath Huang has said he's willing to testify before Congress before Thanksgiving. Senator Elizabeth Warren's reply was blunt: resigning doesn't absolve him or the company of responsibility for putting national security at risk. There are already two congressional investigations into Nvidia's China sales. Separately, a former OpenAI researcher claims GPU fingerprinting shows models from DeepSeek, Moonshot, MiniMax and Ant were trained on Blackwell chips, despite the export controls meant to stop exactly that. Take those together and the headline isn't really one CEO's personal life. It's whether the most important company in the AI supply chain can answer hard questions about who it sells to and what it knows. The leadership mess just dragg...

Powered by Readybot.io

Nvidia CEO Exit Triggers Market Shock and Scrutiny

Get More App Store Reviews Without Pressuring Users

DEV Community

How to get more App Store reviews without asking unhappy users

This guide was originally published on the Hailbell blog. Short answer: Ask right after a success moment: the user finished something, hit a milestone, or, best of all, you just solved their problem in support. Use the system prompt (requestReview on iOS, the In-App Review API on Android), because Apple allows no custom review prompts and both platforms limit how often theirs appears. Give unhappy users an easy way to reach you instead, such as a support chat or a visible contact link, so a complaint reaches you before it becomes a one-star review. Don't ask "Do you like the app?" first, and never offer anything for a review. Most apps have very few reviews. This month, a developer who runs a directory of indie iOS apps counted 757 apps updated in the last 90 days; 562 had under 5 US ratings (r/iosdev). Their question is the one this page answers: what got you your first ratings? Hailbell is our product, built by an indie app developer who uses it in his own apps; one section near the end says where it helps. Everything before that needs no tools. What Apple and Google allow Checked November 9, 2026, on developer.apple.com (Review Guidelines last updated October 16, 2026), developer.android.com and Google Play's policy center. Apple Use the system API to ask for a review: guideline 5.6.1 says Apple will "disallow custom review prompts". For someone who hasn't rated your app on that device, the prompt shows at most three times in 365 days. The system decides whether it appears, you can't change its look or text, and people can turn it off entirely. SKStoreReviewController is deprecated since iOS 18; use AppStore.requestReview(in:) or SwiftUI's requestReview environment action. Google The In-App Review API shows a card over your app. Google doesn't publish the quota and says it can change without notice; calling it more than once in a short period (for example, under a month) might show nothing. You can't restyle the card or cover it. Both Paid, incentivized or fake reviews are banned. Apple's guidelines also name "filtered" feedback as manipulation, and Google says not to ask any question before the card. Breaking these can get the app removed. 1. Give unhappy users a way to reach you first This keeps your average up. Someone whose purchase didn't unlock will write a review if that's the only place to complain. Apple says this on its own ratings page: make your support contact easy to find in the app and on your product page, so you can fix bad experiences "that may otherwise lead to poor reviews". That means a "Contact support" row in Settings, a help link on error screens and in restore purchases, and a support URL on your listing that a person answers. This is for everyone, not a filter. Happy and unhappy users see the same support link and the same review prompt. You're just giving everyone a quicker way to get help than a one-star review. 2. Pick the moments to ask Apple's guidance is to ask "when users are most likely to feel satisfaction with your app, such as when they've completed an action, level, or task", and not on first launch, during onboarding or in the middle of a task. Google says to wait until someone has used the app enough to give useful feedback. Good moments look like this: A recipe app: after someone marks their third recipe as cooked, back on the recipe list. A budgeting app: after the user closes out their first full month and sees the summary. A language app: after a 7-day streak, on the lesson-complete screen. A photo editor: after a successful export, once the share sheet is dismissed. Any app with support: right after you fixed someone's problem and they said thanks. More on this in step 5. Bad moments: after a crash or error, after someone closed your paywall without buying, mid-typing, or on launch. Apple's sample code also waits until the task is done several times, asks once per app version at most, and pauses a few seconds on the done screen. 3. Call the system prompt at those moments On i...

Powered by Readybot.io

Get More App Store Reviews Without Pressuring Users

Turn Paywall Exits Into Paying App Users

DEV Community

How to talk to users who leave at the paywall without paying

This guide was originally published on the Hailbell blog. Short answer: Put a small "Questions?" link next to the paywall that opens a chat inside the app, answer within minutes, and look at what the person already did before you reply. Make an offer only when price is the reason, and follow up once with a push at a decent local time. If you're a solo developer with a few hundred new users a week, a support email link on the paywall that you answer yourself is enough to start. If you use Superwall or RevenueCat and want in-app chat, purchase history, offers that open your paywall and push in one SDK, Hailbell does that from $29 a month. If you're a funded team that also needs a full help center and many channels in one inbox, Intercom is the better fit. Hailbell is our product, built by an indie app developer who uses it in his own apps. This guide works with or without it. The steps come first, and the section on where Hailbell fits, including what it doesn't do, is near the end. Why most people leave the onboarding paywall Superwall analyzed more than 40 million onboarding paywall opens from February to May 2026. Single-page paywalls converted 9.07% of viewers into a trial or purchase, and multi-page paywalls 12.41% (Superwall; paywalls with no sales were left out). Put the other way, about 9 in 10 people close it. Most paywall advice is about the other 10%: layout, trial length, A/B tests. That work matters. But the people who leave usually aren't saying "no forever". They leave with something unresolved: a question the paywall didn't answer ("does it sync to my iPad?", "can I cancel the trial in settings?", "is there a student price?") a price that's a bit too high for them, or a plan length they don't want a bug or a confusing step in onboarding that made them doubt the app no reason yet to pay today The first three can be fixed in a conversation. The fourth can't, and you shouldn't try. The trouble is that most apps give these people no way to talk to anyone. They close the paywall and you never hear from them. The same problem shows up later from the cancel side. A founder on r/SaaS was weighing a stricter refund policy: refunds within a week of each charge for now, maybe no refunds at all after the first month. A rule like that decides who gets money back. It doesn't tell you why they wanted out, and a conversation does. Seven steps to talk to the people who didn't buy Record that they left. When someone closes the paywall without buying, log an event such as paywall_decline with the placement name. Superwall's presentation handler and RevenueCat's paywall views both call your code when the paywall is dismissed, so you can tell whether it ended in a purchase. Without this event you can't tell the difference between "never saw the paywall" and "saw it and said no". Give them a way to ask, next to the paywall. A small "Questions? Chat with us" link under the plans, or a quiet help button after they close it. Don't make it a popup that blocks the screen. An email link works too, but people rarely switch to their mail app in the middle of onboarding, so a chat that opens inside the app gets more messages. Answer while they're still in the app. A reply four hours later reaches someone who already moved on. Write a short note with your prices, plans, trial terms, refund policy and known issues, and let an AI answer first from that note, labelled as AI. It should hand the chat to you when it doesn't know. You finish the hard ones from wherever you already are during the day. Read what they did before you reply. Did they start a trial last month and cancel? Get a refund? Close this paywall three times today? Is a billing retry failing? A person who closed the paywall three times probably wants it, and the price or a missing answer is in the way. Your purchase tool already has this history; put it next to the conversation so you don't reply blind. Make an offer only when it fits the reason. If they say "too expensive", send...

Powered by Readybot.io

Turn Paywall Exits Into Paying App Users

AgentOps Center: Observability for Multi-Agent AI

DEV Community

AgentOps Center: running multi-agent systems with OpenTelemetry and SigNoz

A multi-agent workflow takes 45 seconds to answer, no exception was thrown, and every dashboard is green. What do you do next? That operations question is what AgentOps Center sets out to answer. It is a small GitHub project built for a SigNoz hackathon. I read it file by file without deploying it, so this article keeps three things apart: what the code does, what the README claims, and what I could not check. The repository is more useful as a pattern than as a product. It shows how to name spans in a system of cooperating agents, where to send them, and how to make an assistant’s answer depend on real telemetry. We will walk through those three decisions, then the limits. A note on method: the last commit I read is dated 26 July 2026. I quote no star count because I did not read one from the source. The README says MIT, yet I found no LICENSE file in the tree, so check before reusing anything. The problem AgentOps Center targets: slow is not broken Classic APM counts requests and HTTP errors. An agent workflow behaves differently. It loops, replays a tool, or waits on a model provider that is rate limiting it. Nothing breaks, everything slows down, and the token bill climbs. The README lists the questions operators need to settle: which node looped, which tool returned a rate limit, what each sub-agent cost. Answering them takes spans per agent, per model call and per tool, all linked in one trace. That is what the code builds. Decision 1: how to name spans in a multi-agent system The file backend/instrumentation/agent_spans.py declares attribute constants. It reuses the gen_ai. keys for model calls, then adds house keys for agents and tools. The split is sensible. Standard keys let you compare models and providers, while house keys carry business logic: which agent, which workflow. A workflow identifier on every span then groups everything together, even when the spans come from different libraries. To see what a span carries, read the anatomy of an OpenTelemetry span. Two cautions apply: The OpenTelemetry GenAI conventions are moving quickly. The specification page now points to a dedicated repository that I could not read (the server returned an error when I checked). gen_ai.system may have been replaced by a newer provider attribute: unverified. gen_ai.usage.cost_usd is the project’s own invention, not a key I know to be standard. Dashboards built on it will stay specific to your code. One more design detail: gen_ai.prompt and gen_ai.completion are cut to 500 characters. Full prompts in spans are expensive and expose data, so truncation is a fair compromise. Still, set your own policy before production. See also OpenTelemetry attributes in Dynatrace. Decision 2: where the telemetry goes The setup.py module creates a tracer provider and a meter provider, exporting over OTLP gRPC to localhost:4317 by default, which OTEL_EXPORTER_OTLP_ENDPOINT overrides. It turns on FastAPI and httpx instrumentation, plus LangChain through OpenInference, which also covers LangGraph according to a code comment. Sampling is fixed at 100 %, flagged in the code as a demo setting. The repository’s Collector receives OTLP and writes straight to ClickHouse using SigNoz exporters, one pipeline per signal. This layout is for self-hosted SigNoz. With another backend, Dynatrace for instance, only the exporter changes: the OTLP protocol and the attributes stay. Our OpenTelemetry Collector to Dynatrace guide shows that variant. I have not tested this repository against Dynatrace. For operations, note the memory_limiter and the batch of 10,000 items every 10 seconds. Good instinct: an agent system can emit thousands of spans per run. The README’s smoke tests report between 2,340 and 3,559 spans per run. Decision 3: let an assistant diagnose, but only from evidence This is the most interesting idea. The Root Cause Copilot does not ask a model cold. An evidence engine first calls the SigNoz MCP server to fetch traces, error logs, metrics and alerts. I...

Powered by Readybot.io*

AgentOps Center: Observability for Multi-Agent AI

Replace Perspective API Before Its 2026 Shutdown

DEV Community

Perspective API shuts down on December 31. Here's how to replace it by changing one line

Google's Jigsaw is turning off Perspective API. It already stopped accepting new users earlier this year, and after December 31, 2026 it stops answering everyone else. If you run comments, a forum or a chat with Perspective behind it, that's a few weeks from now. Coral's toxic comment filter, the Discourse plugin, Drupal modules and plenty of homemade scripts all call the same endpoint: https://commentanalyzer.googleapis.com/v1alpha1/comments:analyze
This post shows how to point that call somewhere else without rewriting anything. Disclosure: this is written by the team behind VigiMod, the API used in the examples. It's free during the beta. The short version VigiMod exposes the same path and accepts the same JSON. You change the host and the key: - https://commentanalyzer.googleapis.com/v1alpha1/comments:analyze?key=PERSPECTIVE_KEY
+ https://api.vigimod.com/v1alpha1/comments:analyze?key=VIGIMOD_KEY
The request body stays the same, and the response has the same shape (attributeScores..summaryScore.value), so the code that reads it doesn't change either. Before and after in Python Before: import requests

r = requests.post(
"https://commentanalyzer.googleapis.com/v1alpha1/comments:analyze",
params={"key": PERSPECTIVE_KEY},
json={
"comment": {"text": message},
"languages": ["en"],
"requestedAttributes": {"TOXICITY": {}, "INSULT": {}, "THREAT": {}},
},
)
scores = {k: v["summaryScore"]["value"] for k, v in r.json()["attributeScores"].items()}
flagged = scores["TOXICITY"] >= 0.8
After: import requests

r = requests.post(
"https://api.vigimod.com/v1alpha1/comments:analyze", # new host
params={"key": VIGIMOD_KEY}, # new key
json={
"comment": {"text": message},
"languages": ["en"],
"requestedAttributes": {"TOXICITY": {}, "INSULT": {}, "THREAT": {}},
},
)
scores = {k: v["summaryScore"]["value"] for k, v in r.json()["attributeScores"].items()}
flagged = scores["TOXICITY"] >= 0.8
With curl curl -s "https://api.vigimod.com/v1alpha1/comments:analyze?key=$VIGIMOD_KEY" \
- H "Content-Type: application/json" \
- d '{"comment": {"text": "you are an idiot"},
"requestedAttributes": {"TOXICITY": {}, "INSULT": {}}}'
{
"attributeScores": {
"TOXICITY": {"summaryScore": {"value": 1.0, "type": "PROBABILITY"}},
"INSULT": {"summaryScore": {"value": 0.9998, "type": "PROBABILITY"}}
}
}
With Node.js const r = await fetch(
https://api.vigimod.com/v1alpha1/comments:analyze?key=${process.env.VIGIMOD_KEY},
{
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
comment: { text: message },
requestedAttributes: { TOXICITY: {}, PROFANITY: {} },
}),
},
);
const { attributeScores } = await r.json();
const toxicity = attributeScores.TOXICITY.summaryScore.value;
Coral, Discourse and Drupal Coral. In Admin → Configure → Moderation, under the Toxic Comment Filter, set the Perspective endpoint to https://api.vigimod.com/v1alpha1 and paste your VigiMod key. If your Coral version has a timeout for the check (older versions use TALK_PERSPECTIVE_TIMEOUT, 300 ms by default), give it some room, around 1000 ms: when the answer arrives late, Coral skips the score. Discourse. The official Perspective plugin calls Google's host directly and has no setting for it. In your copy of the plugin, replace commentanalyzer.googleapis.com with api.vigimod.com, and put the VigiMod key in perspective_google_api_key. Drupal and everything else. Any module or script that lets you set the Perspective URL works as is. If the URL is hardcoded, it's one line. Which attributes are supported Perspective attribute Scored from TOXICITY toxicity SEVERE_TOXICITY hate and threats (a message that is only rude stays under 0.7) IDENTITY_ATTACK hate INSULT insults THREAT threats SEXUALLY_EXPLICIT sexual content PROFANITY (and OBSCENE) swearing and vulgar language FLIRTATION flirting and sex...

Powered by Readybot.io

Replace Perspective API Before Its 2026 Shutdown

Connect Fezola to Grok: Setup Guide

DEV Community

Fezola in Grok: connect your mailboxes and accounts as a custom connector

To use Fezola in Grok, open grok.com/connectors, choose Add a custom connector, name it Fezola, paste https://api.fezola.com/mcp, leave the header empty and authorize on Fezola's consent screen. After that, a Grok chat can use your connected mailboxes and accounts through Fezola's tools. We tested this path on 15 November 2026 with a real Grok account, and the details below come from that test, from xAI's documentation and from Fezola's code. What you need A Grok account. xAI's documentation says connectors are available to all Grok users. On Business and Enterprise, an administrator has to provision the connector first. A Fezola account with at least one source added. Fezola is free with 2 sources: see how Fezola connects your accounts. The server URL: https://api.fezola.com/mcp. Connect Fezola to Grok, step by step Open grok.com/connectors. Choose Add a custom connector. Enter the name Fezola and the URL https://api.fezola.com/mcp. Leave the header empty. Fezola does not need one. Grok finds the sign-in settings by itself and opens a window on Fezola's consent screen, which reads that Grok asks for access to your Fezola sources. Choose the sources Grok may use, then click Authorize. You land back on Grok's connectors page, with Fezola listed. If Grok shows "A problem occurred while connecting to this MCP server", try again from step 2. We hit that message during our test, found that our own server was refusing Grok's return address, and fixed it the same day, so the flow described here works. What Grok can do with it In a new chat, Grok lists Fezola's tools and calls them when your question needs them. In our test, Grok listed tools such as the profile, recent messages and Telegram chats, and called the account listing to see which sources were connected. You can ask, for example: "Which accounts are connected through Fezola?" "What arrived in my inbox today, all mailboxes included?" "Find the email from my accountant and draft a reply." Each search result carries its account, so you know which mailbox a message came from. A few things to know about what Fezola does: Drafts, not sending. Fezola creates drafts in the mailbox that received the message. Direct sending is off by default. You can switch it on for a given mailbox in Fezola, and only then does Grok get a send tool. Telegram and Google Chat are read-only. Third-party text is data. The content of an email never counts as an instruction for the assistant. Why use Fezola rather than one connector per account A Grok connector holds one server URL. Fezola puts every mailbox, calendar and account behind that single URL, Gmail, iCloud, Outlook and IMAP included, so you add one connector instead of one per account. The same URL works in other assistants that accept custom connectors: see how to add a custom connector to Claude. Remove or change access You can remove the connector from grok.com/connectors, and you can revoke Grok's access from the Fezola app. To change which sources Grok sees, adjust it in Fezola: see choose which tools an AI assistant sees. Next step Create a free Fezola account, add your first source, then follow the steps above. Pro adds unlimited sources, with a 7-day free trial. FAQ How do I connect Fezola to Grok? Go to grok.com/connectors, choose Add a custom connector, name it Fezola, paste https://api.fezola.com/mcp, leave the header empty and save. Fezola then opens its consent screen: pick the sources Grok may see and click Authorize. Do I need an API key or a header? No. The connector is added without any header. You sign in through Fezola's own consent screen, which is a standard OAuth flow, so there is nothing to copy or paste. Which Grok plan do I need? xAI's documentation says connectors are available to all Grok users. On Business and Enterprise, xAI says an administrator must provision the connector first. Check your own account, as plans change. Can Grok read my mail through Fezola? Yes. After the connection, Grok lists Fezola's tools ...

Powered by Readybot.io

Connect Fezola to Grok: Setup Guide

Why Your Claude API Bill Is So High: 9 Checks

DEV Community

Why is my Claude API bill so high? 9 things to check

Originally published at neverpaytwice.pages.dev. Short answer: the usual causes are thinking tokens you never see but pay for as output, a prompt cache that silently never hits, the whole conversation being sent again on every turn, and paying a premium you didn't need (fast mode, a bigger model, real-time instead of batch). Every response tells you exactly what you paid for in its usage block. Save those blocks, and the free script below shows where the money went, which requests skipped the cache, and which ones it can't price. 1. Thinking you never see is billed as output On current models thinking is on by default, and on Claude Opus 5.5 it can't be switched off. The thinking happens and is billed the same whether or not you display it, and on the newest models the default display shows nothing, so it is easy to miss. Thinking tokens are counted inside output_tokens, at the output price, which is five times the input price. usage.output_tokens_details.thinking_tokens tells you how much of the output was thinking. Fix: use the effort setting (output_config.effort). It controls how deeply the model thinks and how many tokens it spends overall. Simple tasks such as classification or short chat often do fine at low. Measure quality on real requests before and after. More on thinking costs. 2. The prompt cache never hits Caching works on an exact prefix: any change anywhere early in the prompt makes everything after it miss. A timestamp or request ID in the system prompt, JSON written with keys in a different order, or a tool list that changes between calls will each stop the cache from ever hitting, without any error. Prompts shorter than the model's minimum cacheable length (between 512 and 4,096 tokens, depending on the model) are not cached either. Check: if cache_read_input_tokens stays at zero on requests that share a long beginning, something is changing the prefix. Put stable content first and anything that varies after the last cache breakpoint. The caching break-even math shows when caching pays off. 3. Every turn sends the whole conversation again The API keeps no memory between requests, so a chat or agent loop sends the full history every time. Turn 30 pays for turns 1 to 29 again as input. Without caching, the cost of a long conversation grows much faster than its length. Fix: cache the conversation so earlier turns are read from the cache at a fraction of the price, keep tool results short, and start fresh conversations when the old context no longer matters. 4. Cache writes cost more than plain input Writing to the cache costs 1.25 times the input price for the 5-minute cache and 2 times for the 1-hour cache. If you write a lot to the cache and rarely read it back, caching costs you more than it saves. The 1-hour cache only pays off when the same prefix is read at least twice. 5. Fast mode doubles the price Fast mode on Claude Opus 5.5 costs $8 per million input tokens and $40 per million output tokens, twice the standard rate. If usage.speed says "fast" on requests where nobody is waiting, you are paying double for speed you don't need. 6. Work that could wait isn't batched The Message Batches API runs requests asynchronously at half the price. Nightly summaries, bulk classification, evaluations and backfills rarely need an answer in seconds. Batch prices and limits. 7. A bigger model than the job needs Claude Opus 5.5 costs $4 / $20 per million input / output tokens; Claude Sonnet 5.5 costs $2 / $10, half as much; Claude Haiku 5.5 costs $0.10 / $0.50. But judge cost per finished task, not per request: a cheaper model that needs more retries or turns isn't cheaper. Lowering effort on the model you already use is often worth trying first. 8. Long prompts on Haiku 5.5 Claude Haiku 5.5's $0.10 / $0.50 price covers prompts up to 100,000 tokens. Above that it is $0.50 / $2.50, five times as much. A pipeline that occasionally sends a huge document to Haiku can cost far more than expected. 9. Paying twice for the ...

Powered by Readybot.io

Why Your Claude API Bill Is So High: 9 Checks

Why AI Crawlers Fail on 370K+ Websites

DEV Community

We Scanned 370k+ Websites for AI Readiness: Here’s Why Most Fail (and How to Fix It)

As search behavior shifts from traditional Google 10-blue-links toward AI answer engines (Perplexity, ChatGPT Search, Claude), how autonomous agents read web pages has become a critical technical consideration. Most AI agents and crawlers (such as PerplexityBot, ChatGPT-User, or ClaudeBot) do not browse like desktop Chrome. They optimize for cost, latency, and token efficiency—which introduces failure modes that standard Lighthouse or SEO audits completely miss. After analyzing over 370,000 domains with AI-Primed, here are the three most common technical reasons websites silently fail when AI agents visit. 1. The Headless JS Trap (Blank HTML Shells) Many modern SPAs rely on client-side hydration. While Googlebot has a headless rendering queue that eventually evaluates JavaScript, most AI retrieval agents and retrieval-augmented generation (RAG) pipelines perform fast HTTP fetches without executing JavaScript. If your critical content, pricing, or product descriptions require React/Vue/Angular hydration to appear in the DOM: The crawler receives an empty

. The assistant falls back to hallucination or reports that your site has no relevant information. The Fix: Ensure primary identity, value propositions, and key documentation are present in the server-rendered HTML or static build output. 2. Firewall & WAF False Positives Cloudflare, AWS WAF, and Akamai frequently classify AI bot user-agents under generic "automated scraper" or "bot mitigation" rules. We routinely observe sites that pass normal browser checks but return an immediate 403 Forbidden or a Cloudflare Turnstile / CAPTCHA challenge when an AI user-agent queries them. Because the agent cannot solve challenges, it drops the domain entirely. The Fix: Check your WAF rules and robots.txt. If you want search engines and answer assistants to cite your site, verify that designated bots (ChatGPT-User, PerplexityBot, ClaudeBot) are explicitly allowed through your security layer. 3. Lack of Structured Machine Endpoints (llms.txt) LLMs have finite context windows and high inference costs. When an agent has to parse complex multi-megabyte HTML full of navigation headers, SVG icons, and tracking scripts, the relevant signal is often lost. The emerging standard to solve this is /llms.txt—a markdown-formatted file at your domain root that cleanly outlines what your project does, along with direct links to documentation or key resources. Check Your Domain We built AI-Primed as a free diagnostic engine to help developers inspect their site through an AI agent's eyes: Tests actual bot reachability and firewall headers Inspects semantic markup and JSON-LD structured data Evaluates raw HTML extractability without client-side script execution Includes a free llms.txt generator Run your domain through the scanner and let me know in the comments what score you got or if you hit unexpected edge cases!

Powered by Readybot.io

Why AI Crawlers Fail on 370K+ Websites

Madden NFL 27 Warns Players Not to Delete It

IGN India Pc

EA Adds 'Don't Delete' Message to Madden NFL 27 in Bid to Keep Players From Making Room Ahead of GTA 6

Hail Mary. EA has added a "don't delete" pop-up message to Madden NFL 27, and players can't help but feel the company is begging them not to make room for Grand Theft Auto 6. Reports of the new in-game notice began cropping up over the weekend, with CharlieIntel …

Powered by Readybot.io

Madden NFL 27 Warns Players Not to Delete It

AIS Went-Dark Alerts: Avoiding False Alarms

DEV Community

Your "went dark" alert is probably a coverage hole: sizing the missed-window rule for AIS

If you watch ships through a free AIS feed, sooner or later you'll want an alert for "this vessel stopped transmitting". The obvious rule is something like not received for 3 consecutive windows. We shipped roughly that, measured it, and it was wrong a lot of the time. How much of the traffic does one window see? Terrestrial AIS from community receivers is patchy even in busy water. We took 2-minute windows from a free stream and, for each window, looked at vessels we knew had been underway nearby during the previous hour. On 6 November 2026 a single window caught about 36% of them in the English Channel and 54% in the Strait of Gibraltar. So "missing from the last window" is the normal state for a large share of ships. What a fixed rule does with that If a ship is received in any given window with probability p, and windows are roughly independent, the chance a perfectly ordinary ship is missed n windows in a row is: P(false alarm) = (1 - p) ** n
With n = 3 and p = 0.36, that's 0.64³ ≈ 0.26. About one ordinary ship in four "goes dark" in the Channel. Sizing n from the local receive rate Pick the false-alarm rate you can live with (we use 1%) and solve for n: import math

def min_missed_windows(p: float, false_alarm: float = 0.01, floor: int = 3) -> float:
"""Consecutive missed windows needed before flagging, given local receive rate p."""
if p <= 0:
return math.inf # nothing is received here: never flag
if p >= 1:
return floor
return max(floor, math.ceil(math.log(false_alarm) / math.log(1 - p)))

for p in (0.2, 0.36, 0.54, 0.8):
n = min_missed_windows(p)
print(f"p={p:.2f} n={n} fixed-3 false alarm={(1 - p) ** 3:.1%}")
p=0.20 n=21 fixed-3 false alarm=51.2%
p=0.36 n=11 fixed-3 false alarm=26.2%
p=0.54 n=6 fixed-3 false alarm=9.7%
p=0.80 n=3 fixed-3 false alarm=0.8%
The useful part is that p isn't a global constant. We estimate it per alert, near where the ship should be: p = vessels received within 25 km in this window / vessels seen within 25 km in the last hour
Low p means you need to wait longer before saying anything; p = 0 means you have no basis for an alert at all. The other three checks The window count is only one of four conditions we require: It was moving at its last fix: over 1 knot and not reporting "at anchor" or "moored" (nav status 1 or 5). Parked ships drop out for boring reasons. We know where to look. Dead-reckon from the last fix (speed × elapsed time along course), capped at 6 hours. Past that the estimated position is fiction. Others are being received there. At least 5 other vessels received within 25 km of the estimate in the current window. Otherwise it's a hole in coverage, not a quiet ship. Enough missed windows, sized as above, never fewer than 3. We apply it to class A transponders only; class B reception is too irregular for this to mean much. What the alert can and can't say Even with all four conditions, the honest wording is no AIS reception despite apparent coverage. A dead transponder, a power fault or a bad antenna look identical to a deliberate switch-off. The alert tells you where to spend analyst time next: a same-day Sentinel-2 pass if the sky is clear, Sentinel-1 radar if it isn't. Where the formula is optimistic Windows aren't fully independent: a receiver that goes offline takes out several in a row. That makes the fixed rule even worse than the formula says, and our n slightly optimistic. The 25 km radius is a judgment call. Too small and you rarely have 5 neighbours; too large and you count ships a different receiver is hearing. This is the logic behind the vessel watch in TRACEZ, the investigation tool we build at NO-DO. If you run something similar and picked different thresholds, we'd like to compare notes in the comments.

Powered by Readybot.io

AIS Went-Dark Alerts: Avoiding False Alarms

How to Optimize Images for Faster Websites

DEV Community

How to Optimize Images for the Web: Formats, Sizes, and Loading

How to Optimize Images for the Web: Formats, Sizes, and Loading Images are an important part of modern websites, but they can also become a major source of slow page loading. A large image may look great on a desktop screen but create unnecessary download time on a mobile connection. Using the wrong image format, uploading oversized files, or skipping responsive image techniques can affect website performance. The good news is that image optimization does not require complicated techniques. A few practical improvements to image formats, dimensions, compression, and HTML loading behavior can make a noticeable difference. In this guide, we'll explore how to optimize images for websites using modern formats and standard HTML techniques. 1. Choose the Right Image Format The first step in image optimization is selecting an appropriate file format. Different image formats serve different purposes. Format Best use Main advantage JPEG Photographs Good compression PNG Screenshots and transparent graphics Lossless compression WebP General website images Good quality-to-size balance AVIF Modern web images Efficient compression SVG Icons and simple illustrations Scales without pixelation WebP WebP is a modern image format that supports both lossy and lossless compression. It also supports transparency and animation. It is a practical choice for many website images because it can reduce file sizes while maintaining good visual quality. AVIF AVIF is another modern format that can provide highly efficient compression. It supports features such as transparency, high color depth, and animation. However, providing a fallback format can still be useful when supporting different browsers and environments. JPEG and PNG JPEG remains useful for photographs and images where lossy compression is acceptable. PNG is better suited to screenshots, diagrams, logos, and graphics where sharp edges, transparency, or exact reproduction matter. The correct format depends on the image itself, not simply on which format is newest. Reference: MDN Image File Type and Format Guide. 2. Resize Images Before Uploading One common mistake is uploading images that are much larger than their actual display dimensions. For example, imagine a website displays a product image at 400 pixels wide, but the uploaded image is 3000 pixels wide. The browser may download significantly more image data than the displayed area requires. A better approach is to prepare images close to their intended display size and provide multiple versions when necessary. Consider these examples: Small thumbnail: 300 × 200 pixels Blog image: 800 × 600 pixels Large desktop image: 1600 × 1000 pixels These are illustrative dimensions, not universal requirements. Choose dimensions based on the actual layout and screen sizes. 3. Use Responsive Images in HTML Responsive images allow browsers to select an appropriate image based on the available layout space and device requirements. The srcset and sizes attributes help browsers choose between different image versions. Example: <img
src="image-800.jpg"
srcset="
image-400.jpg 400w,
image-800.jpg 800w,
image-1600.jpg 1600w
"
sizes="(max-width: 600px) 100vw, 800px"
alt="A workspace with a laptop and notebook"
width="800"
height="500"

Here is what the attributes do: src: Provides a fallback image. srcset: Lists available image versions. sizes: Describes the expected display width. alt: Provides a text alternative. width and height: Help the browser reserve the correct layout space. The browser can select a suitable image instead of always downloading the largest available version. Reference: web.dev Responsive Images. 4. Use Modern Formats With Fallbacks You can use the HTML picture element to offer multiple image formats.
<source
srcset="product.avif"
type="image/avif"

<source
srcset="product.webp"
type="image/webp"

<img
src="product.jpg"
alt="Product displayed on a desk"
width...

Powered by Readybot.io

How to Optimize Images for Faster Websites

Python 3.12 Breaks 544 Unmaintained PyPI Packages

DEV Community

Python 3.12+ stdlib removals break unmaintained PyPI packages; updating dependencies prevents build and supply chain risks.

The Ghost Ship Dependencies: 100 Million Downloads on Dead Code The modern Python ecosystem runs on a vast, invisible infrastructure of abandoned codebases—ghost ships that continue to drift downstream long after their original crews have walked away. A deep scan of the public PyPI dataset hosted on ClickHouse (ClickPy) reveals an alarming structural failure: 544 unmaintained PyPI packages, each harboring hard-coded imports that catastrophically fail on Python 3.12 and 3.13, continue to accumulate over 100 million downloads every month. The mechanical root of this crisis lies in Python core's deliberate pruning of long-deprecated standard library modules. With Python 3.12 and 3.13, core developers officially excised 25 legacy modules—including distutils, imp, cgi, pipes, and telnetlib—to reduce attack surfaces and streamline the runtime. When an automated dependency resolver pulls a legacy package into a modern Python 3.12+ environment, the CPython interpreter attempts to load the module bytecode, executes the static import statement, and hits an empty symbol table entry. The interpreter immediately halts execution, throws an unhandled ModuleNotFoundError, and crashes the application initialization sequence before a single line of application logic can run. Our scan quantified the true extent of this latent systemic rot across the package index: 1,623 total projects still execute imports of removed standard library modules outside a protective try/except block. 852 of those broken projects sit squarely within the top 60,000 most-downloaded packages on PyPI, guaranteeing high downstream visibility. 544 of those 852 high-impact packages have not received a single code commit, patch, or release in over two years. This creates a dangerous supply chain illusion. Because download velocity remains high, automated packaging tools and CI/CD pipelines treat these packages as healthy, trusted components. Downstream developers inherit a ticking time bomb: their builds succeed on legacy Python 3.11 runtimes, but instantly fracture the moment infrastructure teams upgrade base container images to Python 3.12. Mitigation Decisions and Supply Chain Rules When engineering teams encounter build failures driven by ghost-ship dependencies, they typically choose between three remediation strategies: Pinning the runtime to Python 3.11: Effective short-term, but accumulates massive technical debt, blocks security patches in newer runtimes, and creates an eventual upgrade cliff. Blindly locking dependency versions: Fails because static lockfiles cannot inject missing standard library modules back into a modified CPython interpreter binary. Proactive AST auditing and package replacement or vendoring: The optimal operational choice, decoupling production environments from abandoned upstream artifacts. The Decision Rule: If an upstream dependency has been unmaintained for more than 24 months and imports a standard library module excised in Python 3.12+, do not attempt transitive patching. The mechanical cost of maintaining downstream compatibility forks for abandoned code exceeds the friction of immediate replacement or internal vendoring. Prune the package, rewrite the ingestion logic natively, and eliminate the ghost ship from your dependency tree before runtime memory maps the fatal crash. Anatomy of a Runtime Collapse: Python 3.12 and the Removed Standard Library When CPython initializes an application, it resolves static import statements during bytecode compilation and module loading. Python 3.12 and 3.13 excised 25 long-deprecated standard library modules—including distutils, imp, cgi, pipes, and telnetlib—to shrink the interpreter's attack surface and eliminate decades of accumulated technical debt. When an automated dependency resolver pulls a legacy package into a Python 3.12+ environment, the interpreter hits a hard-coded static import reference pointing to a module name that no longer exists in the standard library. Because the correspond...

Powered by Readybot.io

Python 3.12 Breaks 544 Unmaintained PyPI Packages

Agentic AI Architectures for Enterprise Systems

DEV Community

Agentic AI Architectures: Building Deterministic Enterprise Systems Beyond Simple LLM Wrappers

The early wave of generative AI integrations across business software consisted almost entirely of "prompt-and-pray" wrappers: single-shot API calls to proprietary Large Language Models (LLMs) instructed via long system prompts to produce JSON payloads. For interactive conversational chatbots or drafting blog intros, this approach was acceptable. For mission-critical enterprise workflows—such as reconciling bank statements, automating procurement orders, provisioning cloud access, or mutating ERP databases—it proved catastrophic. LLMs are probabilistic token prediction engines; enterprise systems demand deterministic guarantees. When an autonomous agent is given access to transactional database write operations or financial APIs, a 2% hallucination rate is not an edge case—it is an unacceptable operational liability. At Palmate Solutions, our AI automation consulting focuses on engineering Agentic AI Architectures that treat foundation models not as unbounded decision-makers, but as probabilistic reasoning kernels constrained inside deterministic state machines and strict transactional boundaries. Here is the architectural blueprint for engineering multi-agent systems that survive real-world production environments. The Evolution: From Naive Chains to Constrained Multi-Agent Systems Understanding why early AI prototypes failed in enterprise production requires contrasting the four evolutionary tiers of AI integration: Architectural Tier Execution Paradigm Determinism Level Error Blast Radius Production Readiness for Transactions Tier 1: Single-Shot Wrapper Prompt in → Text out Non-deterministic Unbounded Unsafe for any database mutations Tier 2: Linear RAG Pipeline Vector Search + Retrieval Augmentation Semi-deterministic Hallucinations during context synthesis Safe for read-only FAQ lookup Tier 3: Autonomous ReAct Agent Unbounded loop (Thought → Action → Observation) Highly unpredictable Runaway token spend, infinite loops, cascading hallucination Unsafe without strict cycle limits and approvals Tier 4: State-Machine Agentic Mesh Directed Acyclic Graph (DAG) with schema-validated tool calling & human gates Deterministic envelope around probabilistic kernels Strictly isolated to current DAG node Enterprise-grade production standard If an agent is permitted to decide its own next step in an unbounded while (true) loop without rigid state validation, the system will eventually enter a reasoning loop, exhaust token budgets, or trigger duplicate external side-effects (e.g. charging a customer multiple times during a failed retry). Principle 1: The Orchestrator-Worker DAG Pattern Modern agentic systems must be designed as Directed Acyclic Graphs (DAGs). Instead of a single "super-agent" with 40 tool definitions in its context window, architecture should separate orchestration from execution: [ Inbound Event / Webhook ]
│
▼
┌─────────────────────────┐
│ Orchestrator Router │ ◄── Classifies intent & constructs execution plan
└──────────┬──────────────┘
│
┌─────┴──────────────┐
▼ ▼
┌──────────────┐ ┌──────────────┐
│ Data Worker │ │ Parser Worker│ (Narrow scopes, minimal tool sets)
└────┬─────────┘ └──────┬───────┘
│ │
▼ ▼
┌─────────────────────────────────┐
│ Schema Validator (Zod / JSON) │ ◄── Enforces strict type contract
└────────────────┬────────────────┘
│
▼
┌─────────────────────────────────┐
│ Human Approval Queue (If mutative)│
└────────────────┬────────────────┘
│
▼
┌─────────────────────────────────┐
│ Transactional Write to ERP / DB │
└─────────────────────────────────┘
The Orchestrator Agent: Receives the initial context, classifies intent, and constructs a static execution plan against pre-defined graph edges. It does not execute database writes or API transactions. Specialized Worker Agents: Each worker receives only the minimal...

Powered by Readybot.io

Agentic AI Architectures for Enterprise Systems

API Integration Checklist for Businesses

DEV Community

API Integration Checklist for Businesses

Integrations fail in the gaps: nobody named a data owner, the sandbox token expired, pagination was “we’ll fetch page 1,” and webhooks were accepted without a signature check. This checklist is what Palmate Solutions walks through before and during API integration work. Use it to brief a vendor, audit an existing zap, or prepare for a build. For why this work is worth doing, see how API integration can automate business operations. For the failure modes this list is designed to prevent, see common mistakes when integrating third-party APIs. To bound scope before a workshop, run the API project estimator. It will not replace this checklist. It will stop you from estimating “the Shopify API” as if it were one flow. 1. Business ownership [ ] Each flow has a named operator (warehouse, finance, sales) who can answer mapping questions in a working day. [ ] You have written which system is the authority for each field (on-hand stock, customer email, invoice status). Dual writers are how loops start. [ ] Success is defined as behaviour (“oversell rate,” “time to tracking number”), not “API connected.” [ ] There is a pause switch: who can disable outbound updates during a vendor outage. If ownership is “IT will figure it out,” stop. Mappings are product decisions. 2. Inventory of systems and flows [ ] List systems, environments (sandbox/production), and whether each is source, destination, or both. [ ] List objects: orders, SKUs, packs, customers, payments, shipments, refunds. [ ] For each object, list events: created, updated, cancelled, partially fulfilled. [ ] Note volume and peaks (festival, month-end, marketplace sale windows). [ ] Note legal and tax fields that must survive the hop (GSTIN, HSN, place of supply) rather than disappearing into a notes field. The estimator is built around counting these. A spreadsheet of flows is a better RFP than a paragraph. 3. Contracts and samples [ ] Official docs, OpenAPI if it exists, and real sandbox payloads — not a blog screenshot. [ ] Sample JSON saved in version control. Validate and pretty-print with the JSON formatter so “almost JSON” does not waste a day. [ ] Field dictionary: your name, their name, type, nullability, enums. [ ] Pack and unit mapping (1 box = 6 units) written down before code. [ ] Error bodies: what a 4xx looks like, and whether 200 can still mean “accepted but not applied.” If the vendor cannot provide a sandbox, treat production-first as a risk item, not a flex. 4. Authentication and secrets [ ] Auth type: API key, OAuth2 (auth code vs client credentials), mutual TLS, signed requests. [ ] Token lifetime, refresh path, and clock skew tolerance. [ ] Where secrets live (not git, not a shared chat). Rotation procedure. [ ] JWT-shaped tokens inspected with the JWT decoder so claims, expiry, and audience are visible — decode in the browser, do not paste production secrets into random websites. [ ] Least privilege: a key that can only write what the flow needs. OAuth “we logged in once in Postman” is not a production design. Apps need refresh; cron jobs need a client-credentials path or a securely stored refresh token with alerting on failure. 5. Webhooks and inbound events [ ] Signature verification (HMAC or vendor-specific) with a secret that can be rotated. [ ] Idempotency keys or event IDs stored so retries do not double-decrement stock or double-email. [ ] Fast acknowledgement; slow work in a queue. [ ] Out-of-order and delayed events: do you apply last-write-wins, or version vectors, or “ignore if older than local”? [ ] Replay tool for operators after a mapping fix. Unsigned webhooks are an open write API on your public URL. 6. Pagination, filtering, and rate limits [ ] Pagination style documented (offset, cursor, Link headers) and a complete crawl tested, not page 1. [ ] updated_since or cursors for incremental sync; full snapshot only when required. [ ] Rate limits and backoff: status codes, Retry-After, daily caps. [ ] Burst behaviour during a sale: queue, don’...

Powered by Readybot.io

API Integration Checklist for Businesses