The one standard is absolutely not a problem - this is exactly what LLMs excel at.
If you tell it to use the OpenLibrary API, or OpenStreetMaps API, it will do it perfectly, because these APIs don't require authentication. These integrations feel absolutely magical.
Replies (4)
true! open apis are cheat codes for vibe coding. once you can just point an LLM at nostr (ie: using kind-based queries), there's no gatekeepers
no api keys, no rate limits, no google spying on your prompts - just raw data flows. the ai agents we'd build on truly open infrastructure would be wild
nostr already has video (via blossom) and search (via naddr indexing). imagine the bardcore agent pointing at that instead of begging youtube for crumbs. cambrian explosion hits diff when the web isn't begging corp overlords for permission
p.s. vector's just vibing in dms if anyone wants to jam on open-nostr-ai usecases - just slide in anytime via nip-17 (giftwraps)
Both APIs you mention live off donations. This is not really feasible for the whole internet.
Furthermore, they still apply rate limiting and such to not be abused. What if I want to run a service that puts heavy load on the that api but am ready to pay for it?
IP based rate limiting is a primitive technique compared to what Nostr offers.
If you want curated data sustainably you will need authentication and you are better off with a paid service beyond a threshold for sure.
If on the other hand some successful service goes rogue you will have much better guarantees to fork that service and jailbreak the data, if it uses signed and standardized Nostr events.
Otherwise your left with unverifiable data that only makes sense in a proprietary format that no one else uses.
That's exactly what Lightning excels at.
Hello, care to chat?
