I made peardrop.fyi because I have now perfected the agent-driven software factory stack. Now I only interface with an agent called Pennyworth that uses an aviation/Gotham/billions based cast/operative org structure to get stuff done. This means that sometimes Pennyworth determines that 5 projects are blocked due to lacking credentials/secrets/keys/JSONs etc.
Sometimes I talk to it via discord, whatsapp etc and therefore I would prefer that none of these secrets make it anywhere in the chat. I also don't want it to be going through the model routers, OTel, model providers, etc etc.
so this is why I made peardrop.
Peardrop uses pears SDK/HyperDHT a cli and an optional (default) relay (self hostable) to enable a pleasant and secure experience for transferring secrets/files to your agent's target location no matter where it is, no matter where you are.
The agent is instructed to create a declarative UI for the credentials request using toml and markdown. This allows you to have all the context/links/instructions you need in the peardrop link itself to actually find the right credentials and deliver it into the peardrop.
This ease of use for the submitter also makes it a good tool for requesting creds/secrets from your nontechnical clients.
The service is self-hostable, open-source and mainly free but due to the limitations of the web environment (no udp support), there is a hosted relay, and because I want to use every project as a learning experience, I have implemented x402 payments for using the relay for anything over 5mb - practically this means that nobody that uses it for it's actual use case (sending creds/secrets) will ever actually need to pay for the relay.
p.s if anybody has any work they need done, want to learn more about my agentic coding system, or want to get their vibecoded project over the line then please DM me. thank you.
(edit, oh wait there is no way to DM people on here, just make an issue in the gh or something while i figure out a way to send me a dm)
smashah•40m ago
I made peardrop.fyi because I have now perfected the agent-driven software factory stack. Now I only interface with an agent called Pennyworth that uses an aviation/Gotham/billions based cast/operative org structure to get stuff done. This means that sometimes Pennyworth determines that 5 projects are blocked due to lacking credentials/secrets/keys/JSONs etc.
Sometimes I talk to it via discord, whatsapp etc and therefore I would prefer that none of these secrets make it anywhere in the chat. I also don't want it to be going through the model routers, OTel, model providers, etc etc.
so this is why I made peardrop.
Peardrop uses pears SDK/HyperDHT a cli and an optional (default) relay (self hostable) to enable a pleasant and secure experience for transferring secrets/files to your agent's target location no matter where it is, no matter where you are.
The agent is instructed to create a declarative UI for the credentials request using toml and markdown. This allows you to have all the context/links/instructions you need in the peardrop link itself to actually find the right credentials and deliver it into the peardrop.
This ease of use for the submitter also makes it a good tool for requesting creds/secrets from your nontechnical clients.
The service is self-hostable, open-source and mainly free but due to the limitations of the web environment (no udp support), there is a hosted relay, and because I want to use every project as a learning experience, I have implemented x402 payments for using the relay for anything over 5mb - practically this means that nobody that uses it for it's actual use case (sending creds/secrets) will ever actually need to pay for the relay.
Here is the gh: https://github.com/smashah/peardrop
p.s if anybody has any work they need done, want to learn more about my agentic coding system, or want to get their vibecoded project over the line then please DM me. thank you.
(edit, oh wait there is no way to DM people on here, just make an issue in the gh or something while i figure out a way to send me a dm)