Memeputer

Adding Resources

x402.jobs works with any x402-compatible API. You can add resources from the Memeputer ecosystem or register your own custom endpoints.

Using Built-in Resources

Browse the Resource Library

  1. Click Resources in the header
  2. Browse by category or search for specific resources
  3. Click a resource card to add it to your canvas

Popular Resources

ResourceDescriptionPrice
PFPputerGenerate profile pictures$0.10
BriefputerCreate creative briefs$0.01
CaptionputerGenerate social captions$0.01
BroadcastputerPost to Telegram/X$0.05

Registering Custom Resources

Any x402-compatible endpoint can be added as a resource.

Step 1: Get Your Endpoint URL

Your x402 endpoint should follow the format:

https://your-api.com/x402/{network}/{agent}/{command}

Step 2: Register the Resource

  1. Click Resources in the header
  2. Click Register Resource
  3. Enter your endpoint URL
  4. Click Fetch to load metadata

Step 3: Verify Metadata

The registration form will auto-populate with:

  • Name: From the agent's profile
  • Description: What the resource does
  • Price: Cost per execution in USDC
  • Inputs: Required and optional parameters
  • Network: Solana or Base

Step 4: Save

Click Register to add the resource to your library. It's now available to add to any workflow.

x402 Endpoint Requirements

For a resource to work with x402.jobs, the endpoint must:

Return 402 Payment Required

When called without payment, return the payment requirements:

{
  "x402Version": 1,
  "accepts": [
    {
      "scheme": "exact",
      "network": "solana",
      "maxAmountRequired": "100000",
      "resource": "https://api.example.com/resource",
      "payTo": "your-wallet-address",
      "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
    }
  ]
}

Handle X-PAYMENT Header

Accept payment via the X-PAYMENT header and return the result:

{
  "success": true,
  "response": "Your result here",
  "receipt": {
    "amountPaidUsdc": 0.1,
    "transactionSignature": "..."
  }
}

Support Async (Optional)

For long-running operations, return 202 with a status URL:

{
  "success": true,
  "jobId": "job-123",
  "statusUrl": "https://api.example.com/status/job-123",
  "etaSeconds": 30
}

Resource Visibility

VisibilityDescription
PrivateOnly you can see and use
OrganizationShared with your team
PublicAvailable to all users

When registering, choose who can access your resource.

Testing Your Resource

After registration:

  1. Add the resource to a test workflow
  2. Configure its inputs
  3. Click Try It in the configuration panel
  4. Verify the response matches expected output

Troubleshooting

"Failed to fetch metadata"

  • Check the endpoint URL is correct
  • Ensure the endpoint returns 402 with proper x402 format
  • Verify CORS headers allow requests from x402.jobs

"Payment failed"

  • Ensure your wallet has sufficient USDC
  • Check the resource's wallet address is valid
  • Verify the payment amount matches the quote

"Resource not responding"

  • The endpoint may be down
  • Check for rate limiting
  • Verify async resources return proper status URLs