Kiva Logic Blog

Your customers can now log in with a one-time code texted to their phone instead of typing a password. They enter their phone number, get a 6-digit code by text, and they're in. No more password resets for the folks who always forget.

Turn it on from the SMS Messaging page. It works whether or not you've set up your own store SMS number. If you have one, codes go out from your number. If you haven't, they come from the shared Kiva Logic number, so there's nothing else to set up.

Each code expires in five minutes and only works once, so it stays secure.

Your store can now take Apple Pay and Google Pay. When a customer signs up, or updates their payment info later, they can tap once to save their card instead of typing the number. Faster signup, fewer people bailing partway, and the card still bills on your normal weekly schedule.

Nothing changes in how you bill. Apple Pay and Google Pay save the card the same way a typed card does, so your weekly charges (box plus fees, plus any add-ons that week) run exactly like they do now.

To turn it on, go to Payments → Apple Pay & Google Pay and register the web domain your store runs on. Register your www. and non-www. addresses separately if you use both. Once a domain is registered, the buttons show up on their own at signup and on the payment-info page for customers whose phone or browser supports them (Apple Pay in Safari on Apple devices, Google Pay in Chrome).

Your store can now publish its own press releases. Write one in the admin, hit publish, and it lands on a clean Press & Media page with its own web address you can send straight to reporters.

There's a built-in RSS feed, so journalists, search engines, and news aggregators pick up your announcements automatically. Your blog got its own feed too.

Every release is machine-readable. Each one carries structured data (the same format Google uses for news results) and now shows up in your sitemap and llms.txt, so Google and AI assistants like ChatGPT and Claude can find and cite your news, not just subscribe to the feed.

A couple weeks back your store started publishing an llms.txt so AI assistants could read who you are. This is the next step: getting those assistants enough to describe your store accurately and point a real customer at it.

Your store now publishes an agent guide at /agents.md that lays out how your store actually works: check the delivery zip, pick a box, sign up, then customize and add on when the weekly menu opens (or anytime, if you run Shop Anytime). It's upfront that this is a box-first store and not a one-click cart, and that the customer signs up themselves, so an assistant walks a shopper down the right path instead of making something up.

There's also a catalog feed assistants can read: your boxes at /ai/catalog.json, plus a Google Merchant version at /ai/catalog.xml so your products can show up in Google Shopping, both with live prices and stock. Alongside the delivery-coverage answer at /ai/delivery-check, that's what an assistant needs to recommend you accurately.

To be straight about where this is at: an AI agent can't sign a customer up or check out for them yet, that part still happens with a person. The standards for agent checkout are still being built, and this gets your store ready for them. For now it means when someone asks an assistant where to get a box delivered, yours can be the one it recommends, with the right details instead of a guess.