跳过导航
Introducing OpenWebSearch: One router for web search like Exa, Parallel, Brave, Perplexity and more
0:00 / 5:58

Introducing OpenWebSearch: One router for web search like Exa, Parallel, Brave, Perplexity and more

Interfaze (YC P26)

@interfaze_ai1999 位关注者

在 X 上查看
288 个赞下载原帖

39,682 次观看

Introducing OpenWebSearch: One router for web search like Exa, Parallel, Brave, Perplexity and more - Normalized output structure - Centralized billing - Built-in fallbacks priorities and more

24 条评论

评论来自 X (Twitter) 上的原帖

  • V 的头像

    @vineetwts

    looks like the next billion dollar thing

    5 个赞

  • guglielmo 的头像

    @_guglielmo

    do you reccomend the best provider for diff searches or do you just query all providers/let the user pick?

    4 个赞

  • Harvey ∇ 的头像

    @yorkeccak

    Super cool!

    3 个赞

  • Lahfir 的头像

    @mdlahfir

    Would be absolutely cool if you can waterfall or parallelize a query on all of them and give a unified output.

    2 个赞

  • Abhinav 的头像

    @abhinavexists_

    its worth keeping a eye on...

    2 个赞

  • Odogwu Machalla 的头像

    @unicodeveloper

    This is cool. Nice!

    1 个赞

  • Jibraan 的头像

    @KadriJibraan

    this is big

    1 个赞

  • Md. Asaad Sayed 🪽 的头像

    @AsaadSayed61

    Y'all hiring by any chance?

    1 个赞

  • Whatever 的头像

    @Whatevercrypto

    Exa, for example, has various features other companies APIs don’t have(I assume) like highlights, deep search etc, do we lose some functionality by using your router?

    1 个赞

  • Interfaze (YC P26) 的头像

    @interfaze_ai

    You can pass specific providers params and get their results using provider_options field

  • Jeff Barg 的头像

    @jeffbarg

    great idea

    1 个赞

  • Saïd Aitmbarek 的头像

    @SaidAitmbarek

    🔥🔥

  • Phil Mizrahi 的头像

    @philippemizrahi

    You should check out @Linkup_platform!

  • Buswe 的头像

    @buswe_com

    Normalizing output across providers saves rewriting your parser every time you swap search backends.

  • Ramanjit Singh 的头像

    @ItzRamanCoder

    the "one api key" pitch is good until you realize you're still babysitting n different response shapes upstream. normalized output is step one, not the unlock.

  • Roj Niyogi 的头像

    @niyogi

    beautiful work - up and running on multify for anyone to use out of the box:

  • Forlais 的头像

    @forlaisgroup

    Useful direction. We work the other end of it with EvaEsi Interests, where you name a subject and approve the sources yourself, so retrieval stays something you can account for.

  • Dennis 的头像

    @dnnskr91

    is every startup now becoming a router? we have gone from ai wrappers to wrapping everything and put a router in front of it

  • arthak 的头像

    @arthak_ttt

    @grok It’s better to use SearXNG or that?

  • ojusave 的头像

    @ojusave

    How can I make a PR?