About the challenge

CALL-E is a developer-first platform for building AI agents that make real phone calls and get real-world tasks done. Instead of stopping at text, your agents can plan a call, dial out, hold a natural conversation, adapt in real time, and return structured results you can act on — all through CALL-E's SDK, API, and MCP. In other words: your agents can finally pick up the phone (and actually get something done while they're on the line). ☎️

In CALL-E: Your Code Is Calling, you'll put that to work. Build and deploy a functional application that uses CALL-E to solve a real business or project problem — customer outreach, appointment scheduling, lead qualification, service coordination, workflow automation, or something no one's tried yet. Whether you're an AI engineer, agent builder, or technical founder, this is your chance to push a brand-new platform in directions its makers haven't imagined, share feedback that shapes the roadmap, and compete for a share of $10,000 in prizes.

 

Why join

   :calling: Build something real. Ship an AI agent that completes actual tasks over the phone — not a demo that just generates text.
   :rocket: Work with a new platform first. Get hands-on early with CALL-E's SDK, API, and MCP, and help shape what it becomes.
   :beetle: Shape the roadmap. Your feedback and bug reports go straight to the CALL-E team, with prizes for the most useful input.
   :moneybag: Compete for $10,000 in cash prizes, plus meetings with the CALL-E team, blog features, and CALL-E credits.

 

Get started

  1. Install CALL-E and sign in (5 min) by following the installation guide. You'll get a CALL-E account with 20 free calls automatically. Need more? Request additional calls via this form.
  2. Connect it to your agent via MCP, SDK, or API using the integration guide (~30 min).
  3. Browse example skills and apps and brainstorm your build (30 minutes)

Requirements

What to Build

Build and deploy a functional application that uses CALL-E's SDK, API, and MCP to create an impactful business or project use case.

What to Submit

  • Open a pull request to CALL-E's public repository at https://github.com/CALLE-AI/awesome-phone-call-agents.
    • Follow the instructions under the “README” to submit your pull request to the correct Contribution Area (i.e. “Agent Skills,” “Workflow Plugins”, etc.)
  • On the Devpost submission form, provide the URL to your pull request.
  • Include a demonstration video of your project (about three minutes), uploaded to YouTube or Vimeo and made publicly visible.
  • Provide the email address associated with your CALL-E account
  • Optional: Provide a URL to your functional demo application

Two repositories, two jobs — don't mix them up:

🔧 Setting up CALL-E? CALL-E Integrations

📤 Submitting your project? Awesome Phone Call Agents

Hackathon Sponsors

Prizes

$10,000 in prizes
Most Practical Use Case
$4,000 in cash
1 winner

Virtual meeting with the CALL-E team
Blog post feature
20,000 CALL-E credits (~200 USD in value)

Most Innovative Use Case
$3,000 in cash
1 winner

Virtual meeting with the CALL-E team
Blog post feature
20,000 CALL-E credits (~200 USD in value)

Honorable Mention
$1,000 in cash
2 winners

Virtual meeting with the CALL-E team
Blog post feature
10,000 CALL-E credits (~100 USD in value)

Most Valuable Feedback
$200 in cash
5 winners

10,000 CALL-E credits (~100 USD in value)

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

A qualified panel of judges

A qualified panel of judges

Judging Criteria

  • Real World Impact
    Does the project identify a real, specific phone-work problem and make a credible case that it solves it for real users? Is it worth building further for real users after the hackathon — not a generic "AI that makes phone calls" concept.
  • Quality of the Idea
    Is this a creative, non-obvious use of CALL-E that shows genuine understanding of the problem space? Is the contribution (skill, app, plugin, or demo) clear, well-scoped, and reusable by the community?
  • Technical Implementation
    How thoroughly and skillfully does the project use CALL-E? Does the code reflect genuine effort and a working, non-trivial implementation — CALL-E imported and actually called at runtime, not just referenced?
  • Product Experience & Demo
    Does the project deliver a complete, coherent experience, and does the demo video clearly communicate what it does and why it matters?

Questions? Email the hackathon manager

Invite others to compete

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.