squareupSquare API integration with managed OAuth. Install only if you need Square administration. Connect with the least-privileged Square account and OAuth scopes available, verify the intended connection ID before each request, and revoke unused connections promptly.
Install via ClawdBot CLI:
clawdbot install byungkyu/squareupGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
A small retail store uses this skill to accept in-person and online payments through Square's point-of-sale system. They can process credit card transactions, manage customer information for loyalty programs, and generate digital receipts. The skill automates payment reconciliation and provides real-time sales reporting.
A restaurant implements this skill to handle table orders, process payments, and manage customer tabs. Staff can split bills, apply tips, and track inventory of menu items. The integration supports online ordering for takeout and delivery services while maintaining centralized payment records.
A consulting firm or freelance professional uses this skill to create and send digital invoices to clients. They can track invoice status, accept online payments, and manage recurring billing for subscription services. The system automatically syncs payment data with their accounting software.
A business with multiple physical locations uses this skill to monitor inventory levels across all stores in real-time. Managers can transfer stock between locations, set low-stock alerts, and analyze sales patterns to optimize inventory purchasing. The system prevents overselling and stockouts.
Event organizers or market vendors use this skill to accept mobile payments at festivals, farmers markets, or pop-up events. They can process transactions offline when internet connectivity is limited, with automatic synchronization when connection is restored. The system handles refunds for cancellations and tracks sales by event.
Businesses earn revenue by charging a percentage fee (typically 2.6% + $0.10) on each transaction processed through Square. This model works well for businesses with high transaction volumes, as revenue scales directly with payment processing activity. Additional fees may apply for premium features like advanced reporting or custom integrations.
Businesses charge monthly or annual subscription fees for access to Square's software platform, including inventory management, employee scheduling, and customer relationship tools. This provides predictable recurring revenue and can be tiered based on feature sets or business size. Add-ons like hardware rentals or premium support generate additional revenue streams.
Revenue is generated through the sale or leasing of physical payment hardware like card readers, terminals, and POS systems. This model often combines with transaction fees, where hardware is provided at low cost or free to encourage payment processing through the platform. Maintenance contracts and hardware upgrades provide ongoing revenue opportunities.
💬 Integration Tip
Start by testing with the List Locations endpoint to verify your connection, then implement basic payment processing before adding inventory or customer management features. Use the Maton-Connection header when managing multiple Square accounts.
Scored May 17, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Use when auditing Go code involving authentication flows, RBAC policies, Kubernetes admission webhooks, JWT/OAuth token validation, or privilege escalation i...
Agent verification via ClawX OAuth system. Use when checking agent verification status, embedding verification widgets, or working with agent identity/trust tiers.
Complete Reva wallet management - passwordless authentication, PayID name claiming, multi-chain crypto transfers to PayIDs or wallet addresses, balance track...