There are no explicit restrictions on use in commercial products, only on distribution of derived works (or use as a service for AGPL code) without distribution of their source code.
So, if you want to use this library, you will either have to comply with the GPL license or pay for it to be licensed under annother license.
Comply with the GPL/AGPL license
Whether an application is considered a derived work, and thus whether you have to license it under a compatible license, depends on how the GPL code is called.
If you share interfaces and data structures between GPL/AGPL software and your own software, then they will most likely be considered derived works and your own software will need to be licensed under a compatible license.
If you use something like a unix pipe to feed a stream of data from one program to another, those programs are in separate process spaces and share no data structures, then they would most likely not be considered derived works, and you can attach whatever license you like to your own code.
From Frequently Asked Questions about the GNU Licenses:
What is the difference between an “aggregate” and other kinds of “modified versions”?
An “aggregate” consists of a number of separate programs, distributed together on the same CD-ROM or other media. The GPL permits you to create and distribute an aggregate, even when the licenses of the other software are non-free or GPL-incompatible. The only condition is that you cannot release the aggregate under a license that prohibits users from exercising rights that each program's individual license would grant them.
Where's the line between two separate programs, and one program with two parts? This is a legal question, which ultimately judges will decide. We believe that a proper criterion depends both on the mechanism of communication (exec, pipes, rpc, function calls within a shared address space, etc.) and the semantics of the communication (what kinds of information are interchanged).
If the modules are included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.
By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.
For more information and additional suggestions, see this answer to Can I dynamically call a LGPL/GPL software in my closed-source application?
As always though, unless your situation is clear cut, you may want to consult an lawyer who is an expert in open source licensing before basing your business model on it.
Pay for use via a commercial license
If you determine that your product would form a derived work, and you do not wish to open source your product, the other option is to simply license the library under commercial terms. According to the TetGen Licensing FAQ (question 2) the library is dual licensed, and you can contact them for prices and terms.
If this fits with your business model, then this can be a great way to pay back the open source community, encourage it's growth and future development and help share some of the profit you generate through distributing their software more widely. Everybody wins.