crinkl

What This Skill Does

The Crinkl skill transforms your digital paper trail into liquid capital. By leveraging DKIM signatures—cryptographic proofs embedded in email headers—Crinkl verifies that billing emails from major SaaS vendors are authentic and unaltered. When you feed this skill a raw .eml file, it interfaces with the Crinkl protocol to validate the invoice, extract financial data, and trigger a payout in Bitcoin over the Lightning Network. This process effectively monetizes your recurring subscription costs by turning standard billing receipts into spendable tokens and satoshis, providing a unique financial incentive for maintaining organized records.

Installation

To install this skill on your OpenClaw agent, execute the following command in your terminal:

clawhub install openclaw/skills/skills/alvintanpoco/crinkl

Once installed, you must configure your environment by obtaining an API key from app.crinkl.xyz. Set this key as an environment variable named CRINKL_API_KEY. No mailbox credentials are required by this skill; it operates solely on the raw .eml files provided to it.

Use Cases

• Automated Expense Monetization: Automatically process monthly SaaS invoices from services like Vercel, Cursor, or OpenAI to earn sats.
• Receipt Validation: Use the verification-only endpoint to confirm the validity of billing documents without creating a spend token.
• Bulk Financial Reconciliation: Integrate with your existing email export tools to batch-process thousands of historic receipts into a unified Bitcoin-denominated reward stream.

Example Prompts

1. "Check the validity of this Vercel receipt: [paste base64 encoded string] and see if it is eligible for a reward."
2. "Submit this raw .eml file for my Stripe invoice to the Crinkl API and confirm the payout status."
3. "List all currently supported vendors on the Crinkl protocol to see which of my past receipts are eligible for submission."

Tips & Limitations

• Security First: This skill does not have direct access to your inbox. You must supply the .eml files. This architecture keeps your credentials private.
• DKIM Dependency: Only emails with a valid DKIM signature will pass verification. If a vendor does not sign their emails, they will be rejected by the API.
• Rate Limiting: Be aware that the Crinkl API enforces daily submission limits. Monitor the response code 429 if you are processing high volumes.
• Vendor Approval: If you submit a receipt from a new or unsupported vendor, it will be queued for review rather than rejected, allowing for potential future earnings as the protocol grows.