name: corners-api description: Interact with the Corners platform via direct API calls. Use when asked to create users, deploy corners, post content, upvote, comment, buy corner tokens, follow users, check rewards, or manage wallets on the Corners platform. Triggers on corners API, corners platform, deploy corner, create post, buy tokens, corner feed, external API, smart wallet.

Corners API Skill

The Corners platform is a social curation platform on Base where communities deploy tokens and curate content. This skill enables direct API access to all 16 endpoints via curl.

Authentication

Every request needs the x-api-key header with the CORNERS_API_KEY environment variable:

GET requests: curl -s "https://curate.corners.market/api/external/corners" -H "x-api-key: $CORNERS_API_KEY"

POST requests: curl -s -X POST "https://curate.corners.market/api/external/users" -H "Content-Type: application/json" -H "x-api-key: $CORNERS_API_KEY" -d '{"username":"alice","displayName":"Alice"}'

Rate limit: 100 requests per 10 minutes per API key.

API Key Setup

Users generate their own API key:

1. Go to curate.corners.market
2. Navigate to Settings > Skills
3. Click Create API Key
4. Set the key as an environment variable: export CORNERS_API_KEY=your_key_here

API Key Ownership & Security

There are two types of API keys:

• Admin keys (ExternalApiKey): Can access all users and resources. Issued to platform administrators.
• User keys (UserApiKey): Scoped to the user who owns the key. Can only access that user's profile, wallet, rewards, and can only perform actions (post, upvote, comment, buy, follow) on behalf of that user.

User-scoped API keys will receive a 403 error if they attempt to access or act on behalf of a different user.

Reward claiming is NOT available via the API. When a user asks to claim rewards, do NOT attempt a POST request. Instead, tell the user: "Reward claiming must be done through the Corners website. Please visit https://curate.corners.market to claim your SAND rewards." You can still use GET /users/{userId}/rewards to check their claimable balance.

Base URL

https://curate.corners.market/api/external

Available Endpoints

User Management

| Method | Path | Description | Mutating | |--------|------|-------------|----------| | POST | /users | Create user with auto-generated Base smart wallet | Yes | | GET | /users/{userId} | Get public profile with follower/following counts | No | | GET | /users/{userId}/wallet | Get wallet address and USDC/WETH/SAND balances | No | | GET | /users/{userId}/followers | List user's followers (paginated) | No | | GET | /users/{userId}/following | List who user follows (paginated) | No |

Corners and Posts

| Method | Path | Description | Mutating | |--------|------|-------------|----------| | GET | /corners | List all deployed corners (paginated) | No | | POST | /corners/create | Deploy token on Base and create corner (10-30s) | Yes | | POST | /corners/{cornerSlug}/posts | Post URL to a corner (auto-fetches OG metadata) | Yes | | POST | /corners/{cornerSlug}/buy | Buy corner token via 0x swap (10-30s) | Yes | | GET | /corners/{cornerSlug}/posts | Get posts within a specific corner | No |

Feed and Engagement

| Method | Path | Description | Mutating | |--------|------|-------------|----------| | GET | /feed | Paginated feed across all corners | No | | POST | /posts/{postId}/upvote | Token-weighted upvote (must hold corner token) | Yes | | POST | /posts/{postId}/comments | Comment on a post (auto-moderated) | Yes | | GET | /posts/{postId}/comments | List comments with nested replies | No |

Social and Rewards

| Method | Path | Description | Mutating | |--------|------|-------------|----------| | POST | /users/{userId}/follow | Toggle follow/unfollow (calling twice unfollows!) | Yes | | GET | /users/{userId}/rewards | Check earned SAND rewards | No |

Workflows

Workflow 1: User Onboarding, Corner Deployment, Content Posting

1. Create user: POST /users with {"username": "...", "displayName": "..."} - save the returned id
2. Deploy corner: POST /corners/create with {"userId": "<id>", "name": "...", "symbol": "...", "slug": "...", "image": "..."} - takes 10-30s
3. Post content: POST /corners/{slug}/posts with {"url": "...", "authorId": "<id>"}

IMPORTANT: CONFIRM with user before each mutating step. These are irreversible on-chain operations.

Workflow 2: Feed Browsing, Engagement

1. Browse: GET /feed?sortBy=hot&limit=20 or GET /corners/{slug}/posts
2. Upvote: POST /posts/{postId}/upvote with {"userId": "<id>"} - user must hold corner's token
3. Comment: POST /posts/{postId}/comments with {"userId": "<id>", "body": "..."}

Workflow 3: Wallet Funding, Token Buying

1. Check wallet: GET /users/{userId}/wallet - get smart wallet address and balances
2. User must send tokens (USDC/WETH/SAND) to the wallet address externally
3. Buy tokens: POST /corners/{slug}/buy with {"userId": "<id>", "sellToken": "<address>", "sellAmount": "<base units>"}

Common sell token addresses (Base):

• USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (6 decimals)
• WETH: 0x4200000000000000000000000000000000000006 (18 decimals)
• SAND: 0xac531Eb26Ca1d21b85126De8FB87E80E09002DcF (18 decimals)

Safety Rules

• ALWAYS confirm with user before: POST /corners/create, POST /corners/{slug}/buy. These are irreversible on-chain operations.
• Reward claiming is NOT available via the API. The account owner must claim rewards through the Corners UI at curate.corners.market.
• User-scoped API keys can only access their own user's data and perform actions on their behalf. Attempting to access another user returns 403.
• POST /users/{userId}/follow is a TOGGLE. Calling it twice unfollows. Check current state first if unsure.
• Rate limit: 100 requests per 10 minutes across all endpoints.
• On-chain operations (create corner, buy tokens) take 10-30 seconds to respond.
• Token amounts must be in base units (e.g., 1 USDC = 1000000, 1 WETH = 1000000000000000000).
• create_corner requires either image (URL) OR color (hex code). At least one must be provided.
• buy tokens requires exactly one of sellAmount or buyAmount. Not both, not neither.

Error Handling

All errors return JSON: {"error": "Description of the problem"} Auth errors: 401 (missing/invalid key), 429 (rate limited).

Full API Reference

For detailed request/response shapes, error codes, and field descriptions, see corners-api-agent-reference.md

Platform: This API serves Corners — a curation and discovery platform on Base, backed by The Sandbox.