Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
numlocked
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
numlocked
5d ago
No stress! My first reaction to this was OMG THIS IS AN INCREDIBLE RESOURCE!! We are 100% grateful for this sort of feedback! Here is a direct quote of what I said at 8:17am this morning when someone sent me the article and I scanned it:
2.
▲
by
numlocked
5d ago
Pulled some data - a surprisingly large number of requests to models that generate images, where the user seems to want an image, do NOT return an image. In our chatroom it's ~11%! However, in almost all of those cases, the model is in
3.
▲
by
numlocked
5d ago
We are doing continuous benchmarking of each endpoint, for each provider, and it is very expensive :)
4.
▲
by
numlocked
5d ago
We started actually expiring the credits a ~month ago. If you make any kind of API request, it resets the clock. We try to make it a very generous policy, but we can't keep a monotonically increasing liability on the books. We end up o
5.
▲
by
numlocked
5d ago
We have made MASSIVE improvements here, and network-wide caching rates have been improving relentlessly. We do publish the cache rates for each endpoint; see the "performance" area of our model pages. E.g. https://openr
6.
▲
by
numlocked
5d ago
Will look into this.
7.
▲
by
numlocked
5d ago
Yeah we are very under-staffed. We are hiring aggressively. I readily admit we have inadequate support staffing right now, but we are going as fast as we can to ramp up.
8.
▲
by
numlocked
5d ago
Hmm, let me check. That certainly seems wrong. Can you send me an email w/ your email so I can look into it? im cc at openrouter.ai. Or DM me on X? x.com/cclark
9.
▲
by
numlocked
5d ago
We run benchmarks against all of our endpoints, in production. That first chart that the author shows is in fact our live benchmarking data. If providers underperform, we kick them out of the routing pool. That is why we run those benchma
10.
▲
by
numlocked
5d ago
Co-founder and COO of OpenRouter here. Thanks everyone for the feedback here. Some of this we are aware of, some of it we aren't. Some we can fix, some of it is inherent to inference (and we in fact improve the situation dramatically).
11.
▲
by
numlocked
5d ago
We do now indeed have IP restrictions for API keys
12.
▲
by
numlocked
5d ago
Can you share more about leaking keys?
13.
▲
Kimi K3 Hardware Requirements
(openmodelmap.com)
2 points
by
numlocked
2mo ago
|
0 comments
14.
▲
by
numlocked
4mo ago
Just sent you a DM on twitter!
15.
▲
by
numlocked
4mo ago
Refund policies are clearly documented in our terms. We actually DO offer refunds within 24hrs of credit purchase, which is significantly more flexible than most companies that operate in a similar way. And we try to use good judgement when
16.
▲
by
numlocked
4mo ago
By default (and in most cases) investors and operators are aligned. When we diligence our investors, we call companies they worked with where things didn’t go well, and speak to those founders. Understanding how investors operate when it’
17.
▲
by
numlocked
4mo ago
Yep! Everyone wants a conspiracy, but what I originally posted is in fact the boring truth. Having a bunch of cash in the bank makes for a durable business!
18.
▲
by
numlocked
4mo ago
We have two mechanisms whereby we retain data. Both are opt-in and off by default. One mechanism where you get a discount and we can use the data (in theory this does mean sell it; but our intent is to use it to make efficient dynamic ro
19.
▲
by
numlocked
4mo ago
We have never sold any prompt data to anyone, in any form, and have no plans to do so. Full stop.
20.
▲
by
numlocked
4mo ago
Great investors are helpful, not harmful :) You want accountability from smart, experienced partners!
21.
▲
by
numlocked
4mo ago
Our general theory of the case is that, in the not so distant future, inference will be the second largest opex line item for most companies (behind headcount) and that sourcing, measuring, and governing those tokens is a massive horizontal
22.
▲
by
numlocked
4mo ago
Interesting. Will look into it! We are releasing pass through API params soon which might hit the bid, but is a bit different than what you are describing.
23.
▲
by
numlocked
4mo ago
What differentiation are looking for? We have good documentation of every provider and what their data retention stance is, and you can figure allow/blocklists for all providers. Check out the Guardrails section under settings and tell
24.
▲
by
numlocked
4mo ago
Hi HN! OpenRouter co-founder and COO here. Lots of questions about why we raised! First off: We remain founder-led and founder-controlled, and intend on being here for a long time, creating awesome products for builders all over the world.
25.
▲
by
numlocked
4mo ago
Thanks! We work really hard to make sure we are ready at launch :)
26.
▲
by
numlocked
4mo ago
(openrouter co-founder here) Yeah we should do something to indicate cardinality. I can share that there can often (I'm talking generally; not related to this model in particular) be e.g. a very large app that can be pushing a lot of
27.
▲
by
numlocked
4mo ago
Can you share more? I'm with OpenRouter and we would love to address this! We don't see this in our own testing, I don't believe -- but will share this feedback and dig in.
28.
▲
Opus 4.7's New Tokenizer: What It Costs
(openrouter.ai)
3 points
by
numlocked
5mo ago
|
0 comments
29.
▲
by
numlocked
5mo ago
Doesn’t it seem more plausible that the marketing shots are AI (where the “generated by AI” note appears) rather than the cover designs themselves?
30.
▲
by
numlocked
5mo ago
You are absolutely allowed to expose access to end users, as long as you continue to abide by terms of service. We have hundreds, if not thousands, of apps built on openrouter that in turn have end users of their own. We showcase many of th
More ›