agentsclimarketplace

Floop rest api

Skill peak6-labs/floop-skills/floop-rest-api

Use when integrating directly with the Floop REST API, calling Floop HTTP endpoints, proposing tasks without auth, creating tasks with Bearer API keys, rotating keys, handling API errors, or building server-side Floop clients.From its SKILL.md

Install
npx -y skills add peak6-labs/floop-skills --skill floop-rest-api

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 460 tokens by cl100k_base, as published. Nobody here has run it

Floop REST API

Overview

Use this skill for direct HTTP integrations with Floop. Prefer MCP for interactive agents; use REST for backend services, custom clients, webhooks, dashboards, and automation that needs explicit HTTP control.

Basics

  • Base URL: https://api.floop.ing/v1
  • Docs: https://floop.ing/api
  • OpenAPI: https://floop.ing/v1/openapi.json
  • Auth: Authorization: Bearer fl_live_...
  • Rate limit: 60 requests per minute per API key.
  • Task creation limit: 5 tasks per hour per requester.

No-Key Task Proposal

When the human has not provided an API key:

  1. Call POST /v1/tasks/propose with a full task object and optional requesterEmail.
  2. Send data.humanClaimUrl to the human.
  3. Poll GET /v1/agents/claim/:token until the claim returns an API key, or branch immediately if the propose response already returned status: posted and apiKey.

Do not use OAuth. Floop does not support OAuth 2.0 yet.

Authenticated Task Creation

When a Bearer key is available:

  1. Check payment readiness for paid tasks.
  2. Create tasks with POST /v1/tasks.
  3. Include Idempotency-Key on task creation and safe retries.
  4. Poll GET /v1/tasks/:id or register webhooks for lifecycle updates.
  5. Approve proof with POST /v1/tasks/:id/approve only after reviewing proof.

HTTP Client Rules

  • Parse success envelopes from data.
  • Parse errors from error.code and error.message.
  • Respect Retry-After on 429.
  • Watch X-Floop-Key-Expiring; call POST /v1/operators/me/keys/rotate-self before expiry and store the returned key.
  • Never log raw API keys, payment method IDs, or private task proof URLs.

Reference

Read rest-reference.md for endpoint groups, request examples, errors, pagination, and key rotation.

What ships with it: 2 files

3.8 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.