agentsclimarketplace

Floop rest api

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

Floop agent skills

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.

What its author says it does

Copied from the file, not written here

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.

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.

Gives 0 of the 12 instructions most apis services skills give in 460 tokens

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

  • use plural nouns for resource namesin 41 of 424, across 32 files
  • use cursor-based pagination for large datasetsin 35 of 424, across 20 files
  • include rate limit headers in responsesin 25 of 424, across 13 files
  • Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
  • version APIs in the URL pathin 19 of 424, across 9 files
  • use semantic HTTP status codesin 18 of 424, across 8 files
  • verify webhook signaturesin 18 of 424, across 11 files
  • use query parameters for filteringin 17 of 424, across 6 files
  • use async database operationsin 14 of 424, across 7 files
  • wrap successful responses in a data fieldin 13 of 424, across 3 files
  • prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
  • set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

  • Call the proposal endpoint without an API key
  • Send the human claim URL to the requester
  • Poll the claim endpoint until an API key is returned
  • Check payment readiness for paid tasks
  • Poll task status or register webhooks for updates
  • Review proof before approving tasks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.